Triple
T4476401
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Gigabit Ethernet |
E100018
|
entity |
| Predicate | maxSegmentLength_1000BASE-T |
P15978
|
FINISHED |
| Object | 100 m |
—
|
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 m | Statement: [Gigabit Ethernet, maxSegmentLength_1000BASE-T, 100 m]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: maxSegmentLength_1000BASE-T Context triple: [Gigabit Ethernet, maxSegmentLength_1000BASE-T, 100 m]
-
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.
maximumStationsPerSegment
Indicates the greatest number of stations that are allowed or can exist within a single segment.
-
D.
maximumCableDiameter
Indicates the largest cable diameter that is allowed or supported in a given context or configuration.
-
E.
maximumChannelWidth
Indicates the greatest allowable or observed width of a channel in the given context.
- 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_69b34553cbe48190afa8ac1cac285b86 |
completed | March 12, 2026, 10:59 p.m. |
| NER | Named-entity recognition | batch_69b35728ed508190ba0e882fa62d8848 |
completed | March 13, 2026, 12:15 a.m. |
| PD | Predicate disambiguation | batch_69b3563d63008190816e37027e761375 |
completed | March 13, 2026, 12:11 a.m. |
Created at: March 12, 2026, 11:35 p.m.