Triple
T14113222
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 1999 AFC Championship Game |
E339696
|
entity |
| Predicate | isRivalryGame |
P87828
|
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: [1999 AFC Championship Game, isRivalryGame, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isRivalryGame Context triple: [1999 AFC Championship Game, isRivalryGame, true]
-
A.
isMajorRivalryFor
Indicates that one entity is a primary or highly significant competitor or adversary to another, often characterized by ongoing, notable, or intense rivalry.
-
B.
playsRivalryGameAgainst
Indicates that one entity participates in a rivalry game as an opponent against another entity.
-
C.
hasRivalryContext
Indicates that there exists a competitive or adversarial relationship between entities within a specific situational or contextual framework.
-
D.
hasRivalryAspect
Indicates that there exists a competitive or adversarial relationship or dimension between entities.
-
E.
associatedWithRivalryGame
chosen
Indicates that there is a connection or involvement between entities specifically in the context of a rivalry game.
- 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_69d81c6a95b481909e39111e0c1f31ee |
completed | April 9, 2026, 9:38 p.m. |
| NER | Named-entity recognition | batch_69de600f992c81908133813f2894dcca |
completed | April 14, 2026, 3:41 p.m. |
| PD | Predicate disambiguation | batch_69de05b2f7e481908a9a7d40153234c0 |
completed | April 14, 2026, 9:15 a.m. |
Created at: April 9, 2026, 10:22 p.m.