Triple
T3737967
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | ZB Commodore |
E79630
|
entity |
| Predicate | finalGenerationOf |
P51143
|
FINISHED |
| Object | Holden Commodore nameplate |
—
|
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: Holden Commodore nameplate | Statement: [ZB Commodore, finalGenerationOf, Holden Commodore nameplate]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: finalGenerationOf Context triple: [ZB Commodore, finalGenerationOf, Holden Commodore nameplate]
-
A.
currentGeneration
Indicates that an entity belongs to or is associated with the presently living or active generation within a temporal or lineage sequence.
-
B.
firstGenerationEnd
Indicates the point in time or event at which the first generation in a sequence, lineage, or process concludes.
-
C.
finalPhaseOf
Indicates that one process, stage, or event constitutes the concluding or last phase of another broader process or sequence.
-
D.
fourthGenerationEnd
Indicates that a lineage, process, or sequence has reached the end of its fourth generation.
-
E.
secondGenerationEnd
Indicates the point in time or event at which the second generation of a lineage, process, or system concludes.
- F. None of above. chosen
Provenance (4 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_69ad8b115610819095b02007da5ca3cb |
completed | March 8, 2026, 2:43 p.m. |
| NER | Named-entity recognition | batch_69adcb3e9248819098d481fe29e1c628 |
completed | March 8, 2026, 7:17 p.m. |
| PD | Predicate disambiguation | batch_69adc048f28c819092bed16a95a3cac1 |
completed | March 8, 2026, 6:30 p.m. |
| PDg | Predicate description generation | batch_69adc198b95481908ca6e4e875aae446 |
completed | March 8, 2026, 6:36 p.m. |
Created at: March 8, 2026, 3:34 p.m.