Triple
T32804408
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | NFC Championship Game 2008 season vs. Arizona Cardinals |
E838981
|
entity |
| Predicate | opponentInGame |
P58158
|
FINISHED |
| Object | Arizona Cardinals |
—
|
NE NERFINISHED |
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: Arizona Cardinals | Statement: [NFC Championship Game 2008 season vs. Arizona Cardinals, opponentInGame, Arizona Cardinals]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: opponentInGame Context triple: [NFC Championship Game 2008 season vs. Arizona Cardinals, opponentInGame, Arizona Cardinals]
-
A.
opponentInScenario
chosen
Indicates that one entity is an adversary or rival of another within a specific scenario, context, or situation.
-
B.
opponentInCase
Indicates that two parties are on opposing sides in the same legal case or proceeding.
-
C.
associatedOpponent
Indicates that one entity is recognized or designated as an opponent or adversary associated with another entity in a given context.
-
D.
laterOpponent
Indicates that one entity becomes the opponent of another at a later time or stage, following an earlier phase or matchup.
-
E.
firstGameOpponent
Indicates that one entity is the opponent faced by another entity in its first game or match.
- 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_69f3493d35208190b4351b4e85f2fa16 |
completed | April 30, 2026, 12:21 p.m. |
| NER | Named-entity recognition | batch_69f6f38159d08190980ad639e08f00f4 |
completed | May 3, 2026, 7:04 a.m. |
| PD | Predicate disambiguation | batch_69f6e3d7bee48190b94e0beb48a1d7fa |
completed | May 3, 2026, 5:57 a.m. |
Created at: May 1, 2026, 1:15 a.m.