Triple
T4775986
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | MSG Network |
E106046
|
entity |
| Predicate | standardDefinitionFeed |
P40937
|
FINISHED |
| Object | 480i SDTV |
—
|
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: 480i SDTV | Statement: [MSG Network, standardDefinitionFeed, 480i SDTV]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: standardDefinitionFeed Context triple: [MSG Network, standardDefinitionFeed, 480i SDTV]
-
A.
standardDefinition
Indicates that something serves as the officially accepted or commonly recognized definition of a term or concept.
-
B.
typicalResolution
Indicates the usual or standard level of detail or clarity at which something (such as an image, display, or representation) is normally rendered or presented.
-
C.
resolutionStandard
Indicates that something conforms to, or is evaluated against, a specified level or standard of resolution (e.g., detail, clarity, or granularity).
-
D.
standardPar
Indicates that two entities are parallel and conform to a recognized or defined standard of parallelism.
-
E.
typicalBroadcastFormat
chosen
Indicates the usual or standard broadcast format in which something (such as a program or content) is typically transmitted.
- 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_69bd43f3074c8190937e7b0a457fe9f1 |
completed | March 20, 2026, 12:56 p.m. |
| NER | Named-entity recognition | batch_69bd69237f80819090713ed62653fb75 |
completed | March 20, 2026, 3:34 p.m. |
| PD | Predicate disambiguation | batch_69bd622be1388190ab5511b589c878c0 |
completed | March 20, 2026, 3:05 p.m. |
Created at: March 20, 2026, 1:21 p.m.