Triple
T20271134
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 10GBASE-E |
E499094
|
entity |
| Predicate | supportsTransmissionDistance |
P139488
|
FINISHED |
| Object | up to 40 km |
—
|
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: up to 40 km | Statement: [10GBASE-E, supportsTransmissionDistance, up to 40 km]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: supportsTransmissionDistance Context triple: [10GBASE-E, supportsTransmissionDistance, up to 40 km]
-
A.
transmissionTypeSupported
Indicates that a particular type of transmission is compatible with or can be used by a given system, device, or component.
-
B.
hasLongerReachThan
Indicates that one entity can extend, influence, or physically reach farther than another entity.
-
C.
usesBasebandTransmission
Indicates that one entity employs baseband transmission, meaning it sends digital signals directly over a communication medium without modulating them onto a higher-frequency carrier.
-
D.
cableLength
Indicates the physical length of a cable connecting or associated with an entity.
-
E.
wireDistance
Indicates the physical separation or length of wire between two connected points or components.
- F. None of above. chosen
Provenance (4 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_69da6275fa6c8190952924930adee150 |
completed | April 11, 2026, 3:02 p.m. |
| NER | Named-entity recognition | batch_69e675de35188190840dc7d04c1d5fd9 |
completed | April 20, 2026, 6:52 p.m. |
| PD | Predicate disambiguation | batch_69e55b1e5e1c8190ba8a5544b1db9e1d |
completed | April 19, 2026, 10:45 p.m. |
| PDg | Predicate description generation | batch_69e56702ad04819099c1c08f28d16809 |
completed | April 19, 2026, 11:36 p.m. |
Created at: April 11, 2026, 11:42 p.m.