Triple
T4376573
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | NFL Replay |
E99020
|
entity |
| Predicate | usesFootageFrom |
P7694
|
FINISHED |
| Object | live NFL game broadcasts |
—
|
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: live NFL game broadcasts | Statement: [NFL Replay, usesFootageFrom, live NFL game broadcasts]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usesFootageFrom Context triple: [NFL Replay, usesFootageFrom, live NFL game broadcasts]
-
A.
usesFootageType
Indicates that one entity employs or incorporates a particular type or category of footage in its content or production.
-
B.
usesImageryOf
Indicates that one entity employs or incorporates visual or sensory imagery that depicts, references, or symbolically represents another entity.
-
C.
usedForRecordingBy
Indicates that something serves as a medium, tool, or device that is employed by an agent to make a recording.
-
D.
mediaOrigin
chosen
Indicates the original source or provenance from which a piece of media (such as an image, video, or audio) was derived or obtained.
-
E.
usesAudioFrom
Indicates that one entity incorporates or relies on the audio content produced or provided by another entity.
- 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_69b3454ea8f48190a49c2436624d6ef6 |
completed | March 12, 2026, 10:59 p.m. |
| NER | Named-entity recognition | batch_69b3523d4e888190b4367ed6aa17d463 |
completed | March 12, 2026, 11:54 p.m. |
| PD | Predicate disambiguation | batch_69b34f557fe8819085032bf7f0cea5dc |
completed | March 12, 2026, 11:42 p.m. |
Created at: March 12, 2026, 11:18 p.m.