Triple
T21276110
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | TIA-606 |
E524390
|
entity |
| Predicate | hasVersion |
P455
|
FINISHED |
| Object | TIA-606-B |
—
|
NE NERFINISHED |
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: TIA-606-B | Statement: [TIA-606, hasVersion, TIA-606-B]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: TIA-606-B Context triple: [TIA-606, hasVersion, TIA-606-B]
-
A.
TIA-606
chosen
TIA-606 is a Telecommunications Industry Association standard that defines guidelines for the administration and labeling of telecommunications infrastructure in commercial buildings.
-
B.
TIA-607
TIA-607 is a Telecommunications Industry Association standard that defines requirements for telecommunications grounding and bonding in commercial buildings and data centers.
-
C.
TIA-569
TIA-569 is a Telecommunications Industry Association standard that specifies pathways and spaces design requirements for commercial building telecommunications infrastructure.
-
D.
TIA-568
TIA-568 is a widely adopted commercial building telecommunications cabling standard that defines structured cabling systems for data and voice networks.
-
E.
TIA-942
TIA-942 is a widely recognized data center infrastructure standard that defines requirements and best practices for the design, cabling, and operation of reliable and scalable data centers.
- F. None of above.
- G. Unsure - the case is ambiguous/there is not enough information to decide.
Provenance (2 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_69e0b516293c819089458ea2ec85f85e |
completed | April 16, 2026, 10:08 a.m. |
| NER | Named-entity recognition | batch_69e736577fd48190a0038a6ac5678668 |
completed | April 21, 2026, 8:33 a.m. |
Created at: April 16, 2026, 4:02 p.m.