Triple
T19398158
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Level 0 |
E485245
|
entity |
| Predicate | humanDriverRole |
P82223
|
FINISHED |
| Object | performs entire dynamic driving task |
—
|
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: performs entire dynamic driving task | Statement: [Level 0, humanDriverRole, performs entire dynamic driving task]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: humanDriverRole Context triple: [Level 0, humanDriverRole, performs entire dynamic driving task]
-
A.
transportationRole
Indicates a role or function that an entity has specifically in the context of providing, operating, or supporting transportation.
-
B.
mobilityRole
Indicates the functional role or capacity an entity has in enabling, supporting, or performing movement or transportation.
-
C.
drivingCharacter
chosen
Indicates that one character is operating or controlling a vehicle or mode of transportation.
-
D.
roleInEngine
Indicates the specific function or responsibility an entity has within an engine or engine-like system.
-
E.
transportRole
Indicates that an entity participates in a transportation process with a specific functional role (e.g., carrier, passenger, cargo, or operator).
- 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_69d8e8d5162481909db12435d9535c1a |
completed | April 10, 2026, 12:11 p.m. |
| NER | Named-entity recognition | batch_69e62574edd08190b5456108d5e3907e |
completed | April 20, 2026, 1:09 p.m. |
| PD | Predicate disambiguation | batch_69e4fd602f008190aa9bc76ae17e4ce1 |
completed | April 19, 2026, 4:05 p.m. |
Created at: April 10, 2026, 1:36 p.m.