Triple
T36290554
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Steyr-Puch 500 |
E893214
|
entity |
| Predicate | designerOfEngineAndDrivetrain |
P52425
|
FINISHED |
| Object | Steyr-Daimler-Puch |
—
|
NE NERFINISHED |
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: Steyr-Daimler-Puch | Statement: [Steyr-Puch 500, designerOfEngineAndDrivetrain, Steyr-Daimler-Puch]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: designerOfEngineAndDrivetrain Context triple: [Steyr-Puch 500, designerOfEngineAndDrivetrain, Steyr-Daimler-Puch]
-
A.
chassisDesigner
Indicates that one entity is the designer or creator responsible for the chassis of another entity.
-
B.
mechanicalDesigner
chosen
Indicates that one entity is responsible for designing or engineering mechanical components, systems, or devices for another entity or project.
-
C.
powertrainComponentOf
Indicates that one entity is a component or subsystem that forms part of the powertrain of another entity.
-
D.
cylinderHeadDesigner
Indicates that one entity is the designer or creator responsible for the design of a cylinder head associated with another entity.
-
E.
chiefEngineer
Indicates that one entity serves as the primary or lead engineer responsible for overseeing engineering activities for 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_69f76e4955c08190b8cfddca34fc0242 |
completed | May 3, 2026, 3:48 p.m. |
| NER | Named-entity recognition | batch_69ff41645c548190b7cb4e53079b93ef |
completed | May 9, 2026, 2:15 p.m. |
| PD | Predicate disambiguation | batch_69ff410aa33c8190869ba769ac2a93ce |
completed | May 9, 2026, 2:13 p.m. |
Created at: May 3, 2026, 4:09 p.m.