Triple
T10649249
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ford 385-series V8 |
E250918
|
entity |
| Predicate | camshaftPosition |
P25585
|
FINISHED |
| Object | cam-in-block |
—
|
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: cam-in-block | Statement: [Ford 385-series V8, camshaftPosition, cam-in-block]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: camshaftPosition Context triple: [Ford 385-series V8, camshaftPosition, cam-in-block]
-
A.
steeringWheelPosition
Indicates the relative location or orientation of a steering wheel with respect to a reference point, such as a vehicle’s interior layout or driving side.
-
B.
valvetrainControl
Indicates a control relationship in which one entity regulates or manages the operation of an engine’s valvetrain system.
-
C.
exhaustPosition
Indicates the spatial location or configuration of an exhaust outlet relative to the object it belongs to.
-
D.
crankshaftType
Indicates the specific design or configuration of a crankshaft that an entity uses or is associated with.
-
E.
shaftOrientation
chosen
Indicates the directional alignment or angle at which a shaft is positioned or oriented relative to a reference frame or object.
- 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_69d6aa5a4c4881908f39be6efe5981e5 |
completed | April 8, 2026, 7:19 p.m. |
| NER | Named-entity recognition | batch_69d6dfe3ea08819094a945ebb7fc4d3a |
completed | April 8, 2026, 11:08 p.m. |
| PD | Predicate disambiguation | batch_69d6dd83b114819098e84dc658e82d7e |
completed | April 8, 2026, 10:58 p.m. |
Created at: April 8, 2026, 9:06 p.m.