Triple
T3223510
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Colts–Titans rivalry |
E67566
|
entity |
| Predicate | beganPlayAsDivisionalRivals |
P12653
|
FINISHED |
| Object | 2002 |
—
|
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: 2002 | Statement: [Colts–Titans rivalry, beganPlayAsDivisionalRivals, 2002]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: beganPlayAsDivisionalRivals Context triple: [Colts–Titans rivalry, beganPlayAsDivisionalRivals, 2002]
-
A.
beganPlayBetweenTeams
Indicates that a game or match has started between the specified teams.
-
B.
divisionRivalry
Indicates a competitive or adversarial relationship between entities that belong to the same division or subgroup within a larger organization or system.
-
C.
firstSeasonOfRivalry
chosen
Indicates the season in which a particular rivalry between entities first began or was officially recognized.
-
D.
foundedAsRivalOf
Indicates that an entity was established specifically to compete with or challenge another entity.
-
E.
rivalryBasis
Indicates the underlying reason, cause, or grounds on which a rivalry between entities is based.
- 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_69ad858b8adc8190ad989712c87a476b |
completed | March 8, 2026, 2:19 p.m. |
| NER | Named-entity recognition | batch_69adae1ae8f08190880d0f0e8539cdbc |
completed | March 8, 2026, 5:12 p.m. |
| PD | Predicate disambiguation | batch_69ad9e0bb6c48190a0659c67d40ee37c |
completed | March 8, 2026, 4:04 p.m. |
Created at: March 8, 2026, 3:08 p.m.