Triple
T1205284
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Chevrolet Camaro |
E25873
|
entity |
| Predicate | engineTypeAvailable |
P17976
|
FINISHED |
| Object | inline-6 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: inline-6 engine | Statement: [Chevrolet Camaro, engineTypeAvailable, inline-6 engine]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: engineTypeAvailable Context triple: [Chevrolet Camaro, engineTypeAvailable, inline-6 engine]
-
A.
offeredEngineType
chosen
Indicates that a particular type of engine is made available or provided as an option in a given context.
-
B.
testedEngineType
Indicates that an engine of a specified type has been subjected to a test or evaluation.
-
C.
fuelTypeSupported
Indicates that a system, device, or component is capable of operating with or is designed to accept a specified type of fuel.
-
D.
notableEngineType
Indicates that an entity is particularly recognized for using or being associated with a specific type of engine.
-
E.
engineSupplier
Indicates a relationship where one entity supplies or provides engines 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_69a4942b30f08190a91c60573e16b5ef |
completed | March 1, 2026, 7:31 p.m. |
| NER | Named-entity recognition | batch_69a4bdc0f8d08190b340012a9eb26275 |
completed | March 1, 2026, 10:29 p.m. |
| PD | Predicate disambiguation | batch_69a4bb5ed2b88190aab992913957e1cf |
completed | March 1, 2026, 10:19 p.m. |
Created at: March 1, 2026, 7:46 p.m.