Triple
T136410
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Chevrolet Bolt EV |
E2755
|
entity |
| Predicate | productionEndAnnouncement |
P429
|
FINISHED |
| Object | 2023 (for original Bolt EV line) |
—
|
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: 2023 (for original Bolt EV line) | Statement: [Chevrolet Bolt EV, productionEndAnnouncement, 2023 (for original Bolt EV line)]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: productionEndAnnouncement Context triple: [Chevrolet Bolt EV, productionEndAnnouncement, 2023 (for original Bolt EV line)]
-
A.
productionEnd
Indicates that a production process, activity, or run has come to its completion or final stopping point.
-
B.
announcedThat
Indicates that one entity publicly communicated or declared a specific fact, decision, or piece of information about another entity or situation.
-
C.
announcedAt
Indicates that an announcement or declaration was made at a specific time or event.
-
D.
announcementDate
chosen
Indicates the date on which an announcement is formally made or becomes publicly known.
-
E.
announcementLocation
Indicates the place or venue where an announcement is made or presented.
- 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_69a2520c0f3481908b0ed054a2fca8d0 |
completed | Feb. 28, 2026, 2:25 a.m. |
| NER | Named-entity recognition | batch_69a257a4edf081908c494c8370c76b9a |
completed | Feb. 28, 2026, 2:49 a.m. |
| PD | Predicate disambiguation | batch_69a25652efdc8190b85b33735a9e6370 |
completed | Feb. 28, 2026, 2:43 a.m. |
Created at: Feb. 28, 2026, 2:30 a.m.