Triple
T14629348
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Immaculate Reception |
E343437
|
entity |
| Predicate | videoReplayUsed |
P115113
|
FINISHED |
| Object | no |
—
|
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: no | Statement: [Immaculate Reception, videoReplayUsed, no]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: videoReplayUsed Context triple: [Immaculate Reception, videoReplayUsed, no]
-
A.
usesInstantReplay
Indicates that an entity employs instant replay technology or review during an event, action, or decision process.
-
B.
hasReplay
Indicates that an event, action, or interaction is available to be viewed or experienced again in a recorded or reconstructed form.
-
C.
replayedOn
Indicates that an event, performance, or recording was played again on a particular medium, platform, or channel.
-
D.
usesVideoReviewWherePermitted
Indicates that an entity conducts video-based reviews in contexts or jurisdictions where such use is legally or otherwise allowed.
-
E.
videoAssistantRefereeInUse
Indicates that a video assistant referee system is currently being used to review or assist with officiating decisions.
- F. None of above. chosen
Provenance (4 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_69d822dffc3c8190aa173b90761bffda |
completed | April 9, 2026, 10:06 p.m. |
| NER | Named-entity recognition | batch_69deb4a7c8fc81909d10c1f563d7d1e7 |
completed | April 14, 2026, 9:41 p.m. |
| PD | Predicate disambiguation | batch_69de657359c88190b082e3e9f86fc1d7 |
completed | April 14, 2026, 4:04 p.m. |
| PDg | Predicate description generation | batch_69de716c17cc8190aeb85296abee85a7 |
completed | April 14, 2026, 4:55 p.m. |
Created at: April 10, 2026, 1:26 a.m.