Triple
T3342412
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | The District |
E70288
|
entity |
| Predicate | finaleDate |
P22754
|
FINISHED |
| Object | 2004-05-01 |
—
|
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: 2004-05-01 | Statement: [The District, finaleDate, 2004-05-01]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: finaleDate Context triple: [The District, finaleDate, 2004-05-01]
-
A.
finalMatchDate
Indicates the calendar date on which the final or deciding match in a series, tournament, or competition takes place.
-
B.
finalShowDate
chosen
Indicates the date on which a show, series, or performance has its last scheduled or final airing or presentation.
-
C.
semifinalDate
Indicates the scheduled calendar date on which a semifinal round of a competition or tournament takes place.
-
D.
endDate
Indicates the point in time at which an event, state, or relationship stops being valid or comes to a conclusion.
-
E.
laterFinale
Indicates that one event, episode, or occurrence serves as a concluding part that happens after another referenced event or finale.
- 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_69ad85a405e48190b6e68de7cf9f319e |
completed | March 8, 2026, 2:20 p.m. |
| NER | Named-entity recognition | batch_69adb1ee711481909c0d921f1b5b8562 |
completed | March 8, 2026, 5:29 p.m. |
| PD | Predicate disambiguation | batch_69ada42df1d48190874bb05f95deefde |
completed | March 8, 2026, 4:30 p.m. |
Created at: March 8, 2026, 3:12 p.m.