Triple
T3925206
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Honda Accord |
E93257
|
entity |
| Predicate | optionalEngineConfiguration |
P17976
|
FINISHED |
| Object | V6 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: V6 engine | Statement: [Honda Accord, optionalEngineConfiguration, V6 engine]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: optionalEngineConfiguration Context triple: [Honda Accord, optionalEngineConfiguration, V6 engine]
-
A.
secondGenerationEngineOption
Indicates that an entity offers or is associated with a second-generation version of an engine as an available option.
-
B.
configurationOptionIn
Indicates that a specific configuration option belongs to, or is defined within, a particular configuration set, context, or system.
-
C.
offeredEngineType
chosen
Indicates that a particular type of engine is made available or provided as an option in a given context.
-
D.
previouslyUsedEngine
Indicates that an engine has been used before in a prior context or application, rather than being new or unused.
-
E.
offeredConfiguration
Indicates that one entity presents or makes available a specific configuration or setup option to another entity.
- 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_69aed96bfa1081908f7b30f2c647dee6 |
completed | March 9, 2026, 2:30 p.m. |
| NER | Named-entity recognition | batch_69aeed7f3cc881909464db1970ba39ae |
completed | March 9, 2026, 3:55 p.m. |
| PD | Predicate disambiguation | batch_69aee7609c4081908000ce12ae827c3f |
completed | March 9, 2026, 3:29 p.m. |
Created at: March 9, 2026, 3:23 p.m.