Triple
T3844646
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Buick Riviera |
E93538
|
entity |
| Predicate | eighthGenerationStartYear |
P51878
|
FINISHED |
| Object | 1995 |
—
|
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: 1995 | Statement: [Buick Riviera, eighthGenerationStartYear, 1995]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: eighthGenerationStartYear Context triple: [Buick Riviera, eighthGenerationStartYear, 1995]
-
A.
sixthGenerationEndYear
Indicates the year in which a sixth generation (e.g., of a product, lineage, or series) comes to an end.
-
B.
sixthGenerationStart
Indicates the point in time or event at which a sixth generation in a sequence, lineage, or series begins.
-
C.
eighthPlanStartYear
Indicates the calendar year in which the eighth plan in a sequence of plans begins.
-
D.
fifthGenerationStart
Indicates the point in time or event at which the fifth generation in a sequence, lineage, or series begins.
-
E.
secondGenerationStartYear
Indicates the calendar year in which the second generation of something (e.g., a product, model, or series) begins.
- 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_69aed96ce578819084ab16e3439976c9 |
completed | March 9, 2026, 2:30 p.m. |
| NER | Named-entity recognition | batch_69aeebb655c081909ec5ff3d09eb4778 |
completed | March 9, 2026, 3:48 p.m. |
| PD | Predicate disambiguation | batch_69aee750377c8190af70c79768c0edd8 |
completed | March 9, 2026, 3:29 p.m. |
| PDg | Predicate description generation | batch_69aee8d9b328819080158be59e5bcc97 |
completed | March 9, 2026, 3:35 p.m. |
Created at: March 9, 2026, 3:18 p.m.