Triple
T30320553
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Volkswagen Crafter |
E771185
|
entity |
| Predicate | firstGenerationAssemblyLocation |
P59462
|
FINISHED |
| Object | Düsseldorf, Germany |
E36993
|
NE 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: Düsseldorf, Germany | Statement: [Volkswagen Crafter, firstGenerationAssemblyLocation, Düsseldorf, Germany]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: firstGenerationAssemblyLocation Context triple: [Volkswagen Crafter, firstGenerationAssemblyLocation, Düsseldorf, Germany]
-
A.
secondGenerationAssemblyLocation
Indicates the place where a second-generation product, component, or entity is assembled.
-
B.
thirdGenerationAssembly
Indicates that an entity is assembled or produced using third-generation manufacturing or assembly processes.
-
C.
firstGenerationStart
Indicates the point in time or event at which the first generation in a sequence, lineage, or series begins.
-
D.
firstGenerationOrigin
Indicates that an entity originates from the first generation within a defined lineage, cycle, or sequence.
-
E.
locationOfAssembly
chosen
Indicates the place where a group, object, or structure is put together, constructed, or assembled.
- F. None of above.
Provenance (4 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_69f22489ee8481909344649bfbb92e83 |
completed | April 29, 2026, 3:32 p.m. |
| NER | Named-entity recognition | batch_6a01ca0db6f08190bed479584114e63d |
completed | May 11, 2026, 12:22 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a277c14c9688190b2a6875c39fca80a |
completed | June 9, 2026, 2:36 a.m. |
| PD | Predicate disambiguation | batch_6a01c96ff4a08190a4fbf0cebbda95b4 |
completed | May 11, 2026, 12:20 p.m. |
Created at: April 29, 2026, 7:52 p.m.