Triple
T27578905
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Back the Way We Came: Vol 1 (2011–2021) bonus EP |
E699528
|
entity |
| Predicate | decadeCoveredEnd |
P105097
|
FINISHED |
| Object | 2020s |
—
|
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: 2020s | Statement: [Back the Way We Came: Vol 1 (2011–2021) bonus EP, decadeCoveredEnd, 2020s]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: decadeCoveredEnd Context triple: [Back the Way We Came: Vol 1 (2011–2021) bonus EP, decadeCoveredEnd, 2020s]
-
A.
endedInDecade
Indicates that an event, process, or state concluded during a specified decade.
-
B.
chronologicalCoverageEnd
Indicates the point in time at which the temporal or chronological span of something (such as a resource, event, or record) comes to an end.
-
C.
endYearApprox
Indicates that the end year of an event, state, or relationship is known only approximately rather than as a precise calendar year.
-
D.
coveredInDecade
chosen
Indicates that an event, activity, or state occurs within and is temporally contained by a specific decade.
-
E.
builtInDecade
Indicates that a structure or object was constructed during a specific decade.
- 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_69ef6a4cb8b881909b3a8d630fd89df2 |
completed | April 27, 2026, 1:53 p.m. |
| NER | Named-entity recognition | batch_69f6359e3d3c81909814e2f0a7fb0ea9 |
completed | May 2, 2026, 5:34 p.m. |
| PD | Predicate disambiguation | batch_69f631871c888190bf29466fe4254e51 |
completed | May 2, 2026, 5:16 p.m. |
Created at: April 27, 2026, 2:02 p.m.