Triple
T3223517
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Colts–Titans rivalry |
E67566
|
entity |
| Predicate | divisionTitleImplications |
P36802
|
FINISHED |
| Object | frequent |
—
|
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: frequent | Statement: [Colts–Titans rivalry, divisionTitleImplications, frequent]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: divisionTitleImplications Context triple: [Colts–Titans rivalry, divisionTitleImplications, frequent]
-
A.
divisionImplications
Indicates the consequences, outcomes, or effects that result from a particular division or separation between entities.
-
B.
divisionTitle
Indicates the formal name or title assigned to a specific division within a larger organization or structure.
-
C.
divisionTitleAtStake
chosen
Indicates that a particular division title is being contested or can be won in the referenced event or matchup.
-
D.
divisionTitles
Indicates that an entity holds or is associated with one or more titles or championships within a specific division or category.
-
E.
divisionAssociation
Indicates an organizational relationship where one entity functions as a division, branch, or sub-unit of another entity.
- 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.