Triple
T10423703
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Maybach HL 120 TRM |
E245729
|
entity |
| Predicate | crankshaftSupport |
P6547
|
FINISHED |
| Object | 7 main bearings |
—
|
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: 7 main bearings | Statement: [Maybach HL 120 TRM, crankshaftSupport, 7 main bearings]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: crankshaftSupport Context triple: [Maybach HL 120 TRM, crankshaftSupport, 7 main bearings]
-
A.
crankshaftType
Indicates the specific design or configuration of a crankshaft that an entity uses or is associated with.
-
B.
propulsionShafts
Indicates a relationship where shafts are used to transmit mechanical power for propulsion between components of a system.
-
C.
shaftCount
chosen
Indicates the number of shafts associated with or contained in an object or system.
-
D.
shaftOrientation
Indicates the directional alignment or angle at which a shaft is positioned or oriented relative to a reference frame or object.
-
E.
connectingRodArrangement
Indicates the specific way in which connecting rods are configured or arranged relative to each other and associated components in a mechanism or engine.
- 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_69d381bf3dc08190bf35a2643e4e8f22 |
completed | April 6, 2026, 9:49 a.m. |
| NER | Named-entity recognition | batch_69d4ea2de4d48190aee65b3f6ec3cc48 |
completed | April 7, 2026, 11:27 a.m. |
| PD | Predicate disambiguation | batch_69d4dfb9d3648190aaabed901f22a8c0 |
completed | April 7, 2026, 10:43 a.m. |
Created at: April 6, 2026, 12:12 p.m.