Triple
T18395732
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Destino |
E449862
|
entity |
| Predicate | resumedProductionYear |
P91011
|
FINISHED |
| Object | 1999 |
—
|
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: 1999 | Statement: [Destino, resumedProductionYear, 1999]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: resumedProductionYear Context triple: [Destino, resumedProductionYear, 1999]
-
A.
productionStartYear
Indicates the year in which the production of an item, work, or entity first began.
-
B.
constructionResumptionYear
Indicates the year in which a previously halted or paused construction activity was resumed.
-
C.
revivalYear
chosen
Indicates the year in which something (such as a work, practice, or institution) was brought back into active use or renewed after a period of decline or inactivity.
-
D.
enteredSeriesProduction
Indicates that an item has transitioned from development or prototype status into regular, large-scale manufacturing or series production.
-
E.
compilationYear
Indicates the year in which a work, collection, or set of materials was compiled or assembled into its final form.
- 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_69d8b9fab8a8819086a9ddc0871715e0 |
completed | April 10, 2026, 8:51 a.m. |
| NER | Named-entity recognition | batch_69e51846bb4c8190990f42a792a78ee0 |
completed | April 19, 2026, 6 p.m. |
| PD | Predicate disambiguation | batch_69e44ff1f92c8190afbb8e85d12bf2a9 |
completed | April 19, 2026, 3:45 a.m. |
Created at: April 10, 2026, 10:46 a.m.