Triple
T29422741
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | ATF Dingo 1 |
E746197
|
entity |
| Predicate | chassisBase |
P7999
|
FINISHED |
| Object | Mercedes-Benz Unimog |
—
|
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: Mercedes-Benz Unimog | Statement: [ATF Dingo 1, chassisBase, Mercedes-Benz Unimog]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: chassisBase Context triple: [ATF Dingo 1, chassisBase, Mercedes-Benz Unimog]
-
A.
chassis
chosen
Indicates that one entity serves as the structural frame or supporting base (chassis) for another entity.
-
B.
chassisConstruction
Indicates how the chassis of an object is built or assembled, specifying the construction method or structural design used.
-
C.
chassisOrigin
Indicates the place or source from which a chassis was originally produced, manufactured, or derived.
-
D.
chassisFeature
Indicates that a particular feature, component, or characteristic is part of or associated with a chassis.
-
E.
chassisCode
Indicates the specific chassis designation or code assigned to a vehicle model to distinguish its underlying structural platform or variant.
- 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_69f0a79f6d5c8190a350baed0157e06f |
completed | April 28, 2026, 12:27 p.m. |
| NER | Named-entity recognition | batch_69f66a6aa3d08190887bfa4eed48faeb |
completed | May 2, 2026, 9:19 p.m. |
| PD | Predicate disambiguation | batch_69f66339175c819080bd70f0ff7057b1 |
completed | May 2, 2026, 8:48 p.m. |
Created at: April 28, 2026, 3:06 p.m.