Triple
T2108381
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | SMPTE ST 2022 |
E42446
|
entity |
| Predicate | uses |
P98
|
FINISHED |
| Object | RTP |
E123450
|
NE 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: RTP | Statement: [SMPTE ST 2022, uses, RTP]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: RTP Context triple: [SMPTE ST 2022, uses, RTP]
-
A.
RTP
chosen
RTP (Real-time Transport Protocol) is a network protocol designed for delivering audio and video over IP networks in real-time, commonly used in streaming, VoIP, and multimedia communication systems.
-
B.
RTP buses
RTP buses are a publicly operated bus network in Mexico City that provides surface transit services and connections to the city’s metro system.
-
C.
RTM
RTM is the commonly used abbreviation for Rosetta Terminology Mapping, a system for standardizing and aligning terminology across different datasets or domains.
-
D.
SRT
SRT was the former name of Toronto’s Line 3 Scarborough, an elevated light rapid transit line that operated in the city’s eastern suburbs.
-
E.
PTP
PTP is a network-based time synchronization protocol defined by the IEEE 1588 standard that enables highly precise clock alignment across distributed systems.
- F. None of above.
- G. Unsure - the case is ambiguous/there is not enough information to decide.
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_69a8871040f08190aac2e2d0ab6b47ad |
completed | March 4, 2026, 7:25 p.m. |
| NER | Named-entity recognition | batch_69abbae03f308190841f5a419bb821f6 |
completed | March 7, 2026, 5:42 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69ae306ff3a481909ce3c34edb3ab0e2 |
completed | March 9, 2026, 2:29 a.m. |
Created at: March 4, 2026, 7:43 p.m.