Triple
T11571336
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Acura MDX |
E274392
|
entity |
| Predicate | availableConfiguration |
P66130
|
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: [Acura MDX, availableConfiguration, V6 engine]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: availableConfiguration Context triple: [Acura MDX, availableConfiguration, V6 engine]
-
A.
configurationAvailable
chosen
Indicates that a specific configuration option or setup is present and can be used or applied in the given context.
-
B.
offeredConfiguration
Indicates that one entity presents or makes available a specific configuration or setup option to another entity.
-
C.
availableAs
Indicates that one entity can be used, accessed, or offered in the form, role, or capacity of another entity.
-
D.
availableWith
Indicates that one entity can be obtained, accessed, or used in conjunction with another entity.
-
E.
availableFor
Indicates that one entity can be used, accessed, or allocated for the benefit, purpose, or use of 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_69d6aae5ac3c81908d2b0a3a665665b2 |
completed | April 8, 2026, 7:22 p.m. |
| NER | Named-entity recognition | batch_69d88dd6913881908becf188c0a7a275 |
completed | April 10, 2026, 5:42 a.m. |
| PD | Predicate disambiguation | batch_69d85dc3fc2c8190bed7e2111301a77c |
completed | April 10, 2026, 2:17 a.m. |
Created at: April 8, 2026, 9:38 p.m.