Triple
T24545260
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Studebaker V8 engine |
E607204
|
entity |
| Predicate | camshaftLocation |
P99215
|
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: [Studebaker V8 engine, camshaftLocation, cam-in-block]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: camshaftLocation Context triple: [Studebaker V8 engine, camshaftLocation, cam-in-block]
-
A.
camshaftType
Indicates the specific design or configuration of camshaft associated with an engine or mechanical system.
-
B.
camshaftConfiguration
chosen
Indicates how the camshafts are arranged or configured within an engine’s valve train system.
-
C.
enginePlacement
Indicates the spatial or structural position where an engine is located or mounted relative to another object or system.
-
D.
powertrainLocation
Indicates the physical placement or mounting position of a vehicle’s powertrain relative to the rest of the vehicle.
-
E.
crankshaftType
Indicates the specific design or configuration of a crankshaft that an entity uses or is associated with.
- 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_69e2c4c9bf94819082d05da6f5c29907 |
completed | April 17, 2026, 11:39 p.m. |
| NER | Named-entity recognition | batch_69f2be044d4c819094e14eda28d371a7 |
completed | April 30, 2026, 2:27 a.m. |
| PD | Predicate disambiguation | batch_69f2a6b0ca8081908d931aec560eae56 |
completed | April 30, 2026, 12:47 a.m. |
Created at: April 18, 2026, 2:26 a.m.