Triple
T108667
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Dallas Cowboys–Washington Commanders rivalry |
E2194
|
entity |
| Predicate | team2Established |
P5807
|
FINISHED |
| Object | 1932 |
—
|
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: 1932 | Statement: [Dallas Cowboys–Washington Commanders rivalry, team2Established, 1932]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: team2Established Context triple: [Dallas Cowboys–Washington Commanders rivalry, team2Established, 1932]
-
A.
team1LaterKnownAs
Indicates that the first team was later renamed to or became known by the identity of the second team.
-
B.
team2
Indicates that the second team involved in a competitive or collaborative context is associated with a given entity or event.
-
C.
team2Franchise
Indicates a relationship where a second team is associated with, or belongs to, a particular franchise.
-
D.
team1
Indicates that the referenced entity is the first team or side participating in a competitive or relational context.
-
E.
team1Franchise
Indicates that an entity serves as or represents the franchise associated with the first team in a given sports or competitive 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_69a24fcdaeb48190a2d796677e4b3281 |
completed | Feb. 28, 2026, 2:15 a.m. |
| NER | Named-entity recognition | batch_69a25711f6788190a22252ea3a3af394 |
completed | Feb. 28, 2026, 2:46 a.m. |
| PD | Predicate disambiguation | batch_69a2563fd2fc819090265edbfe3092d6 |
completed | Feb. 28, 2026, 2:43 a.m. |
| PDg | Predicate description generation | batch_69a2570f45bc81909ebba7ee5f602976 |
completed | Feb. 28, 2026, 2:46 a.m. |
Created at: Feb. 28, 2026, 2:20 a.m.