Triple
T31981374
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | One More Chance |
E816588
|
entity |
| Predicate | nextSingleYear |
P45802
|
FINISHED |
| Object | 2013 |
—
|
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: 2013 | Statement: [One More Chance, nextSingleYear, 2013]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: nextSingleYear Context triple: [One More Chance, nextSingleYear, 2013]
-
A.
nextYear
Indicates that one time point occurs in the calendar year immediately following another time point.
-
B.
nextSingleReleaseYear
chosen
Indicates the calendar year in which the entity’s next individual (non-album) release is scheduled or occurred.
-
C.
nextEventYear
Indicates the calendar year in which the subsequent occurrence of a given event takes place.
-
D.
nextSingle
Indicates that one entity is the immediately following single item in a sequence or ordered set relative to another entity.
-
E.
nextWorkReleaseYear
Indicates the year in which the next work in a sequence or series is scheduled to be released.
- 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_69f348f6a3008190bfb59ca695fd68e2 |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_69f6b34d116c81908086e458fe8bf42e |
completed | May 3, 2026, 2:30 a.m. |
| PD | Predicate disambiguation | batch_69f6b151ad008190836c1bcdec503ce2 |
completed | May 3, 2026, 2:22 a.m. |
Created at: May 1, 2026, 12:11 a.m.