Triple
T23001547
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Toyota Auris Excel |
E572644
|
entity |
| Predicate | engineOptionsInclude |
P82736
|
FINISHED |
| Object | 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: petrol engine | Statement: [Toyota Auris Excel, engineOptionsInclude, petrol engine]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: engineOptionsInclude Context triple: [Toyota Auris Excel, engineOptionsInclude, petrol engine]
-
A.
engineModelOption
chosen
Indicates that a particular engine model is available as a configurable option for an item or product.
-
B.
wheelOptionsInclude
Indicates that a given set of wheel options contains or offers a specified wheel type or configuration.
-
C.
engineTypeIncluded
Indicates that a specified engine type is included as part of, or supported within, another entity or configuration.
-
D.
engineConfigurationSupport
Indicates that one entity provides or defines support for a particular engine configuration of another entity.
-
E.
outputIncludes
Indicates that the result or product of a process, function, or action contains or incorporates a specified element or component.
- 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_69e245b6a3ac81908087599eefe3e365 |
completed | April 17, 2026, 2:37 p.m. |
| NER | Named-entity recognition | batch_69f18353d05481909abacb48a14ef21e |
completed | April 29, 2026, 4:04 a.m. |
| PD | Predicate disambiguation | batch_69ef3b9cd5488190bcd23183179f48cd |
completed | April 27, 2026, 10:34 a.m. |
Created at: April 17, 2026, 3:50 p.m.