Triple
T17483257
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | IEEE 802.3u |
E425715
|
entity |
| Predicate | definesMaximumSegmentLength |
P15978
|
FINISHED |
| Object | 100 meters for 100BASE-TX |
—
|
LITERAL FINISHED |
How this triple was built (2 steps)
Every LLM step that produced this triple, in pipeline order — named-entity classification, the disambiguation choices (the exact options shown, with the pick highlighted), and the generated description. The batch + timestamp of each is in the Provenance table below.
NER
Named-entity recognition
gpt-5-mini
Instruction
Given a phrase, classify it is english named entity (e.g., persons, organizations, works of art) in Latin script, or not (e.g., literals, dates, URLs, verbose phrases). For disambiguation, the statement where the phrase occurs as object is also given. Please return a JSON object with `phrase` (string, the phrase being analyzed) and `is_ne` (boolean, indicating whether the phrase is a Named Entity).
Input
Phrase: 100 meters for 100BASE-TX | Statement: [IEEE 802.3u, definesMaximumSegmentLength, 100 meters for 100BASE-TX]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: definesMaximumSegmentLength Context triple: [IEEE 802.3u, definesMaximumSegmentLength, 100 meters for 100BASE-TX]
-
A.
maximumSegmentLength
chosen
Indicates the greatest allowable or observed length of a segment within a given context or structure.
-
B.
maximumNumberOfSegments
Indicates the greatest allowable or observed count of discrete segments into which something can be or is divided.
-
C.
maxSingleCanalLength
Indicates the maximum length of any single canal segment associated with an entity.
-
D.
maximumStationsPerSegment
Indicates the greatest number of stations that are allowed or can exist within a single segment.
-
E.
definesMaximum
Indicates that one entity specifies or sets the upper limit or greatest allowable value for another entity.
- F. None of above.
Provenance (3 batches)
The batch behind each pipeline step, in order, with when it ran. Timestamps are batch-level — stages were processed in waves, so the object chain (NER → NED1 → NEDg → NED2) reads in order, but predicate / elicitation batches can sit in a different wave.
| Step | Stage | Batch ID | Status | When |
|---|---|---|---|---|
| creating | Elicitation | batch_69d889dccf7481909264a1844a2e9100 |
completed | April 10, 2026, 5:25 a.m. |
| NER | Named-entity recognition | batch_69e451d06c2881909632845dd7a6b1e3 |
completed | April 19, 2026, 3:53 a.m. |
| PD | Predicate disambiguation | batch_69e3b4f341c88190adabe526d8903b05 |
completed | April 18, 2026, 4:44 p.m. |
Created at: April 10, 2026, 5:48 a.m.