Triple
T16807081
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | J150 |
E408507
|
entity |
| Predicate | typicalEngineOptions |
P105374
|
FINISHED |
| Object | petrol V6 engines (varies by market) |
—
|
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: petrol V6 engines (varies by market) | Statement: [J150, typicalEngineOptions, petrol V6 engines (varies by market)]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: typicalEngineOptions Context triple: [J150, typicalEngineOptions, petrol V6 engines (varies by market)]
-
A.
typicalEngine
Indicates that an entity is the standard or commonly used engine for another entity (such as a vehicle, device, or system).
-
B.
typicalOption
chosen
Indicates that one option is considered standard, common, or most representative among a set of possible options.
-
C.
engineModelOption
Indicates that a particular engine model is available as a configurable option for an item or product.
-
D.
typicalPerformanceSetting
Indicates the usual or most common context, venue, or environment in which a performance or activity typically takes place.
-
E.
secondGenerationEngineOption
Indicates that an entity offers or is associated with a second-generation version of an engine as an available option.
- 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_69d88393905081908d00a86b99996ac8 |
completed | April 10, 2026, 4:58 a.m. |
| NER | Named-entity recognition | batch_69e3b2cd1e8c8190a7a05ba255f711c7 |
completed | April 18, 2026, 4:35 p.m. |
| PD | Predicate disambiguation | batch_69e32b814b188190aee525f8779203cd |
completed | April 18, 2026, 6:58 a.m. |
Created at: April 10, 2026, 5:22 a.m.