Triple
T644025
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Mercedes-Benz |
E11202
|
entity |
| Predicate | introducedTechnology |
P14232
|
FINISHED |
| Object | crumple zone |
—
|
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: crumple zone | Statement: [Mercedes-Benz, introducedTechnology, crumple zone]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: introducedTechnology Context triple: [Mercedes-Benz, introducedTechnology, crumple zone]
-
A.
technologyPioneered
chosen
Indicates that an entity was the first or among the first to develop, introduce, or significantly advance a particular technology.
-
B.
introduced
Indicates that one entity caused another entity to become known, presented, or brought into use for the first time to a person, group, or context.
-
C.
introducedConcept
Indicates that one entity is responsible for presenting, defining, or bringing a new concept into use or awareness for another entity or context.
-
D.
technologyType
Indicates the specific kind or category of technology associated with an entity or relationship.
-
E.
technologyLevel
Indicates the degree of technological advancement or sophistication associated with an entity relative to others or to a defined scale.
- 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_69a493266a2881909daf4c40f719dee8 |
completed | March 1, 2026, 7:27 p.m. |
| NER | Named-entity recognition | batch_69a49f18216081908331aa12dac40214 |
completed | March 1, 2026, 8:18 p.m. |
| PD | Predicate disambiguation | batch_69a49d0a0ab481909871461418a00be7 |
completed | March 1, 2026, 8:09 p.m. |
Created at: March 1, 2026, 7:36 p.m.