Triple
T32377507
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | DVR-MS |
E827328
|
entity |
| Predicate | storesBroadcastStandard |
P15170
|
FINISHED |
| Object | NTSC |
—
|
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: NTSC | Statement: [DVR-MS, storesBroadcastStandard, NTSC]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: storesBroadcastStandard Context triple: [DVR-MS, storesBroadcastStandard, NTSC]
-
A.
broadcastStandard
chosen
Indicates that one entity uses, supports, or is associated with a particular broadcast transmission standard (such as a TV or radio broadcasting format).
-
B.
broadcastStation
Indicates that one entity functions as a broadcast station that transmits content or signals to an audience or network.
-
C.
broadcastNetwork
Indicates that one entity serves as the television or radio network that broadcasts the programming or content of another entity.
-
D.
broadcastsIn
Indicates that one entity transmits or airs content within a particular medium, channel, location, or time frame.
-
E.
broadcastLiveFrom
Indicates that an event or program is being transmitted in real time from a specific location or source.
- 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_69f349177ddc8190ab0583f05597056b |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_69f6cd126fcc8190aa1f1f146e45ec0c |
completed | May 3, 2026, 4:20 a.m. |
| PD | Predicate disambiguation | batch_69f6cc1470808190b70cdfd7a6395670 |
completed | May 3, 2026, 4:16 a.m. |
Created at: May 1, 2026, 12:51 a.m.