Triple
T10293155
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Red Cashion |
E241412
|
entity |
| Predicate | officiatedGameType |
P92947
|
FINISHED |
| Object | NFL playoff game |
—
|
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: NFL playoff game | Statement: [Red Cashion, officiatedGameType, NFL playoff game]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: officiatedGameType Context triple: [Red Cashion, officiatedGameType, NFL playoff game]
-
A.
officiatedChampionshipGame
Indicates that an entity served as the official (such as a referee or umpire) in charge of overseeing a championship game.
-
B.
ballGameType
Indicates the specific kind or category of ball game associated with an event or activity.
-
C.
typeOfSportOfficial
Indicates that one entity serves as the specific role or type of sports official (e.g., referee, umpire, judge) associated with another entity.
-
D.
notableGameType
Indicates that a game is of a particular type or category for which the subject is especially well known or notable.
-
E.
hasGameType
Indicates that an entity (such as a game or match) is associated with a specific category or type of game.
- 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_69d381aaafc08190af475ef58dc16aba |
completed | April 6, 2026, 9:49 a.m. |
| NER | Named-entity recognition | batch_69d4d2d46fb08190b7694290692e47dc |
completed | April 7, 2026, 9:48 a.m. |
| PD | Predicate disambiguation | batch_69d4d1f35e548190be3b4d92d65d2d20 |
completed | April 7, 2026, 9:44 a.m. |
| PDg | Predicate description generation | batch_69d4d29d7cf08190acd70cee634c5cdb |
completed | April 7, 2026, 9:47 a.m. |
Created at: April 6, 2026, 11:42 a.m.