Triple
T19913960
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Reckless |
E478615
|
entity |
| Predicate | 30thAnniversaryEditionReleaseYear |
P29904
|
FINISHED |
| Object | 2014 |
—
|
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: 2014 | Statement: [Reckless, 30thAnniversaryEditionReleaseYear, 2014]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: 30thAnniversaryEditionReleaseYear Context triple: [Reckless, 30thAnniversaryEditionReleaseYear, 2014]
-
A.
anniversaryEditionPublicationYear
chosen
Indicates the year in which an anniversary edition of a work was published.
-
B.
expandedEditionYear
Indicates the year in which a work’s expanded or enlarged edition was published or released.
-
C.
finalReleaseYear
Indicates the calendar year in which something (such as a product, work, or version) is officially released for the last time.
-
D.
expansionReleaseYear
Indicates the year in which an expansion (such as an add-on, DLC, or extended version) is officially released.
-
E.
anniversaryRemixReleaseYear
Indicates the year in which an anniversary edition or remix version of something (typically a work or product) was 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_69d8e520682081909892916424699bd5 |
completed | April 10, 2026, 11:55 a.m. |
| NER | Named-entity recognition | batch_69e659928030819085a4aafc6a0ef5c8 |
completed | April 20, 2026, 4:51 p.m. |
| PD | Predicate disambiguation | batch_69e537ecda248190895c96afb6243823 |
completed | April 19, 2026, 8:15 p.m. |
Created at: April 10, 2026, 1:53 p.m.