Triple
T35735963
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Walter Bäumer |
E1032887
|
entity |
| Predicate | drivingRole |
P7949
|
FINISHED |
| Object | works driver |
—
|
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: works driver | Statement: [Walter Bäumer, drivingRole, works driver]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: drivingRole Context triple: [Walter Bäumer, drivingRole, works driver]
-
A.
transportationRole
Indicates a role or function that an entity has specifically in the context of providing, operating, or supporting transportation.
-
B.
drivingCharacter
Indicates that one character is operating or controlling a vehicle or mode of transportation.
-
C.
mobilityRole
Indicates the functional role or capacity an entity has in enabling, supporting, or performing movement or transportation.
-
D.
transportRole
chosen
Indicates that an entity participates in a transportation process with a specific functional role (e.g., carrier, passenger, cargo, or operator).
-
E.
drivingPrinciple
Indicates that one entity functions as the core motivating idea, value, or rule that fundamentally guides or directs another entity’s behavior, decisions, or development.
- 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_69f76e10e59081908d81ad9ce22f40b6 |
completed | May 3, 2026, 3:47 p.m. |
| NER | Named-entity recognition | batch_69f7a34f8ee08190a040304635539a8f |
completed | May 3, 2026, 7:34 p.m. |
| PD | Predicate disambiguation | batch_69f7a06f125c8190843af194f042a465 |
completed | May 3, 2026, 7:22 p.m. |
Created at: May 3, 2026, 4:05 p.m.