Triple
T3260133
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Texans–Titans rivalry |
E68388
|
entity |
| Predicate | team2RenamedAsTitans |
P46929
|
FINISHED |
| Object | 1999 |
—
|
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: 1999 | Statement: [Texans–Titans rivalry, team2RenamedAsTitans, 1999]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: team2RenamedAsTitans Context triple: [Texans–Titans rivalry, team2RenamedAsTitans, 1999]
-
A.
team1LaterKnownAs
Indicates that the first team was later renamed to or became known by the identity of the second team.
-
B.
teamName
Indicates the relationship that assigns or associates a specific name with a particular team.
-
C.
team2
Indicates that the second team involved in a competitive or collaborative context is associated with a given entity or event.
-
D.
cityTeam2
Indicates that a team is based in, represents, or is associated with a particular city.
-
E.
team1
Indicates that the referenced entity is the first team or side participating in a competitive or relational context.
- 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_69ad858f74408190bcbd07f967cd7bd0 |
completed | March 8, 2026, 2:19 p.m. |
| NER | Named-entity recognition | batch_69adafa673a481909b5024b4e0e1c2a7 |
completed | March 8, 2026, 5:19 p.m. |
| PD | Predicate disambiguation | batch_69ada41ae74081909a0d1d696be8e35e |
completed | March 8, 2026, 4:30 p.m. |
| PDg | Predicate description generation | batch_69ada525bb2c8190b773efe6d696b6ab |
completed | March 8, 2026, 4:34 p.m. |
Created at: March 8, 2026, 3:09 p.m.