Triple
T12423032
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | GM N platform |
E296823
|
entity |
| Predicate | productionEndApprox |
P4160
|
FINISHED |
| Object | 2005 |
—
|
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: 2005 | Statement: [GM N platform, productionEndApprox, 2005]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: productionEndApprox Context triple: [GM N platform, productionEndApprox, 2005]
-
A.
productionEnd
chosen
Indicates that a production process, activity, or run has come to its completion or final stopping point.
-
B.
initialProductionEndDate
Indicates the date on which the initial phase or run of production for something comes to an end.
-
C.
developmentEnded
Indicates that the process of creating, improving, or expanding something has been completed and no further development is taking place.
-
D.
typicallyEndsAt
Indicates that an event, process, or activity most commonly or usually concludes at a particular time, place, or state.
-
E.
approximateEndUse
Indicates that something is an estimated or inferred final purpose, application, or consumption context of another entity.
- 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_69d6ada0640c81908c061d7fb3d47786 |
completed | April 8, 2026, 7:33 p.m. |
| NER | Named-entity recognition | batch_69d94e1888b48190bd750f839a26e99e |
completed | April 10, 2026, 7:23 p.m. |
| PD | Predicate disambiguation | batch_69d94d354b488190adc83fb4f2770dd5 |
completed | April 10, 2026, 7:19 p.m. |
Created at: April 8, 2026, 9:55 p.m.