Triple
T5995820
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | DB 601A |
E133464
|
entity |
| Predicate | crankshaftPosition |
P25585
|
FINISHED |
| Object | above cylinders (inverted layout) |
—
|
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: above cylinders (inverted layout) | Statement: [DB 601A, crankshaftPosition, above cylinders (inverted layout)]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: crankshaftPosition Context triple: [DB 601A, crankshaftPosition, above cylinders (inverted layout)]
-
A.
crankshaftType
Indicates the specific design or configuration of a crankshaft that an entity uses or is associated with.
-
B.
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.
-
C.
shaftOrientation
chosen
Indicates the directional alignment or angle at which a shaft is positioned or oriented relative to a reference frame or object.
-
D.
shaftCount
Indicates the number of shafts associated with or contained in an object or system.
-
E.
crownPosition
Indicates the relative placement or orientation of a crown with respect to another object or reference point.
- 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_69c00870ddbc81909880fa3864f4f38d |
completed | March 22, 2026, 3:19 p.m. |
| NER | Named-entity recognition | batch_69c04e943dcc8190a09817e8ef0e4188 |
completed | March 22, 2026, 8:18 p.m. |
| PD | Predicate disambiguation | batch_69c049e152e88190979ab80cb9b50321 |
completed | March 22, 2026, 7:58 p.m. |
Created at: March 22, 2026, 4:05 p.m.