Triple
T33406077
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | California Special |
E855440
|
entity |
| Predicate | offeredWithEngine |
P17976
|
FINISHED |
| Object | V8 engine options |
—
|
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: V8 engine options | Statement: [California Special, offeredWithEngine, V8 engine options]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: offeredWithEngine Context triple: [California Special, offeredWithEngine, V8 engine options]
-
A.
offeredEngineType
chosen
Indicates that a particular type of engine is made available or provided as an option in a given context.
-
B.
engineTypeIncluded
Indicates that a specified engine type is included as part of, or supported within, another entity or configuration.
-
C.
availableEngineDisplacement
Indicates the range or specific values of engine displacement that are offered or applicable for a given entity.
-
D.
offersPowertrain
Indicates that one entity provides or makes available a specific powertrain to another entity or for a particular product.
-
E.
engineTypeUsed
Indicates that a particular type of engine is employed or utilized in relation to a specified entity or system.
- 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_69f3496f04a08190804e56ac5098b8e4 |
completed | April 30, 2026, 12:22 p.m. |
| NER | Named-entity recognition | batch_69fd974d75e08190af46b1d608769f3b |
completed | May 8, 2026, 7:57 a.m. |
| PD | Predicate disambiguation | batch_69fd94ff792c8190bedf4a639d3da809 |
completed | May 8, 2026, 7:47 a.m. |
Created at: May 1, 2026, 1:36 a.m.