Triple
T393376
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 1956 Summer Olympics |
E8927
|
entity |
| Predicate | hadLimitedTelevisionCoverage |
P2341
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [1956 Summer Olympics, hadLimitedTelevisionCoverage, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hadLimitedTelevisionCoverage Context triple: [1956 Summer Olympics, hadLimitedTelevisionCoverage, true]
-
A.
isTelevised
Indicates that an event, program, or activity is broadcast on television for public viewing.
-
B.
firstTelevisionBroadcast
Indicates that the subject is the entity responsible for the earliest or inaugural television broadcast of the object.
-
C.
notableEventCoverage
Indicates that there is media or documented coverage specifically focused on a notable event related to the subject.
-
D.
usedForTelevisionBroadcastSchedules
Indicates that something is utilized to organize, present, or manage the timing and content of television broadcast schedules.
-
E.
televisionExposureLevel
chosen
Indicates the degree or amount of exposure an entity has to television content.
- 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_69a2e7f55c60819097aff65ea2ca2832 |
completed | Feb. 28, 2026, 1:04 p.m. |
| NER | Named-entity recognition | batch_69a2ec7637c08190b695ec640edbf6c2 |
completed | Feb. 28, 2026, 1:24 p.m. |
| PD | Predicate disambiguation | batch_69a2e96a8ca48190abbd8de9b02c115c |
completed | Feb. 28, 2026, 1:11 p.m. |
Created at: Feb. 28, 2026, 1:08 p.m.