Triple
T18294034
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | EIA-232 |
E438184
|
entity |
| Predicate | typicalMaximumCableLength |
P83574
|
FINISHED |
| Object | 15 meters |
—
|
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: 15 meters | Statement: [EIA-232, typicalMaximumCableLength, 15 meters]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: typicalMaximumCableLength Context triple: [EIA-232, typicalMaximumCableLength, 15 meters]
-
A.
maxCableLength
chosen
Indicates the maximum allowable length of a cable in the specified context or configuration.
-
B.
maxCableLengthDependsOn
Indicates that the maximum allowable cable length is determined or constrained by another factor, condition, or parameter.
-
C.
cableLength
Indicates the physical length of a cable connecting or associated with an entity.
-
D.
maximumCableDiameter
Indicates the largest cable diameter that is allowed or supported in a given context or configuration.
-
E.
passiveCableMaxSpeed
Indicates the maximum data transmission speed that can be supported when using a passive cable in the relationship.
- 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_69d8b915e3e881909125d760c15d0c29 |
completed | April 10, 2026, 8:47 a.m. |
| NER | Named-entity recognition | batch_69e5010205bc8190a32fe731ead3d988 |
completed | April 19, 2026, 4:21 p.m. |
| PD | Predicate disambiguation | batch_69e44fdf43d08190bbcfb6b1fe3cc0ee |
completed | April 19, 2026, 3:45 a.m. |
Created at: April 10, 2026, 10:35 a.m.