Triple
T10793517
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Dallas Cowboys–Washington Commanders rivalry |
E254643
|
entity |
| Predicate | typicalGameDays |
P34404
|
FINISHED |
| Object | Sunday |
—
|
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: Sunday | Statement: [Dallas Cowboys–Washington Commanders rivalry, typicalGameDays, Sunday]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: typicalGameDays Context triple: [Dallas Cowboys–Washington Commanders rivalry, typicalGameDays, Sunday]
-
A.
typicalNumberOfGamesRange
Indicates the usual minimum and maximum number of games typically played in the associated context or setting.
-
B.
primaryGameDay
Indicates the main or most significant day on which a game or sporting event is scheduled or typically played.
-
C.
typicalMatchDay
Indicates that the relationship or conditions described correspond to what normally happens on a standard or usual match day.
-
D.
typicalEventDay
chosen
Indicates the day on which an event is normally or most commonly held or occurs.
-
E.
numberOfGamesScheduled
Indicates the total count of games that have been planned or arranged for a given entity or time period.
- 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_69d6aa609f008190a294200aefcb7bd5 |
completed | April 8, 2026, 7:20 p.m. |
| NER | Named-entity recognition | batch_69d732f878648190be5e25c56a7511cf |
completed | April 9, 2026, 5:02 a.m. |
| PD | Predicate disambiguation | batch_69d6f316940c819092a96c429629fdef |
completed | April 9, 2026, 12:30 a.m. |
Created at: April 8, 2026, 9:17 p.m.