Triple
T4106253
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Citroën C6 |
E88456
|
entity |
| Predicate | petrolEngineOption |
P4162
|
FINISHED |
| Object | 3.0 L ES9 V6 petrol engine |
—
|
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: 3.0 L ES9 V6 petrol engine | Statement: [Citroën C6, petrolEngineOption, 3.0 L ES9 V6 petrol engine]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: petrolEngineOption Context triple: [Citroën C6, petrolEngineOption, 3.0 L ES9 V6 petrol engine]
-
A.
enginePower
Indicates the power output produced by an engine, typically quantifying its capability to perform work or generate mechanical energy.
-
B.
availableEngineDisplacement
chosen
Indicates the range or specific values of engine displacement that are offered or applicable for a given entity.
-
C.
engine
Indicates a relationship where something functions as, contains, or is driven by an engine as its source of mechanical power or propulsion.
-
D.
numberOfCylinders
Indicates the count of engine cylinders associated with an entity.
-
E.
fuelForm
Indicates the physical or chemical form in which a fuel exists or is supplied (e.g., liquid, gas, solid).
- 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_69aed9484fb881909146f4c772ad277c |
completed | March 9, 2026, 2:29 p.m. |
| NER | Named-entity recognition | batch_69af03d7240c8190a64dcbc669772808 |
completed | March 9, 2026, 5:31 p.m. |
| PD | Predicate disambiguation | batch_69af0183eb84819087d7184de28f5514 |
completed | March 9, 2026, 5:21 p.m. |
Created at: March 9, 2026, 3:40 p.m.