Triple
T2726837
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Oldsmobile Aurora |
E60212
|
entity |
| Predicate | firstGenerationEngine |
P41895
|
FINISHED |
| Object | 4.0 L L47 V8 |
—
|
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: 4.0 L L47 V8 | Statement: [Oldsmobile Aurora, firstGenerationEngine, 4.0 L L47 V8]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: firstGenerationEngine Context triple: [Oldsmobile Aurora, firstGenerationEngine, 4.0 L L47 V8]
-
A.
firstStageEngine
Indicates that an engine functions as the primary propulsion unit used in the first stage of a multi-stage launch vehicle or rocket.
-
B.
firstGenerationProduction
Indicates that the production or creation of something belongs to its initial or earliest generation in a sequence or lineage.
-
C.
firstGenerationStart
Indicates the point in time or event at which the first generation in a sequence, lineage, or series begins.
-
D.
codenameOfFirstGeneration
Indicates that one entity is the codename assigned to the first generation of another entity.
-
E.
firstGenerationEnd
Indicates the point in time or event at which the first generation in a sequence, lineage, or process 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_69ab4b75cd908190b691ef0d1801acda |
completed | March 6, 2026, 9:47 p.m. |
| NER | Named-entity recognition | batch_69abdace9f308190964a064859612cd6 |
completed | March 7, 2026, 7:59 a.m. |
| PD | Predicate disambiguation | batch_69abd82586f88190a98f60d3247fe2d3 |
completed | March 7, 2026, 7:47 a.m. |
| PDg | Predicate description generation | batch_69abd949c120819099a9d56eb71a0339 |
completed | March 7, 2026, 7:52 a.m. |
Created at: March 6, 2026, 9:56 p.m.