Triple
T31429822
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Dallas Cowboys 1990s Super Bowl dynasty |
E801764
|
entity |
| Predicate | endSeasonApprox |
P17000
|
FINISHED |
| Object | 1996 NFL season |
—
|
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: 1996 NFL season | Statement: [Dallas Cowboys 1990s Super Bowl dynasty, endSeasonApprox, 1996 NFL season]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: endSeasonApprox Context triple: [Dallas Cowboys 1990s Super Bowl dynasty, endSeasonApprox, 1996 NFL season]
-
A.
endSeason
chosen
Indicates the action or event of bringing a particular season, series, or period to a close.
-
B.
typicalEndSeason
Indicates the season in which something (such as an activity, event, or condition) usually or characteristically comes to an end.
-
C.
contractEndSeason
Indicates the season in which a contract or agreement is scheduled to end.
-
D.
endYear
Indicates the year in which an event, state, or relationship comes to an end.
-
E.
endYearApprox
Indicates that the end year of an event, state, or relationship is known only approximately rather than as a precise calendar year.
- 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_69f348c475348190bf579ca858eec77c |
completed | April 30, 2026, 12:19 p.m. |
| NER | Named-entity recognition | batch_69f6a5f71b2c8190aade8a83f465be0c |
completed | May 3, 2026, 1:33 a.m. |
| PD | Predicate disambiguation | batch_69f69fe66df08190958558d63ee623d9 |
completed | May 3, 2026, 1:07 a.m. |
Created at: April 30, 2026, 8:56 p.m.