Triple
T19398162
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Level 1 |
E485245
|
entity |
| Predicate | monitoringResponsibility |
P123719
|
FINISHED |
| Object | human 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: human driver | Statement: [Level 1, monitoringResponsibility, human driver]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: monitoringResponsibility Context triple: [Level 1, monitoringResponsibility, human driver]
-
A.
monitoringRequirement
Indicates that one entity is obligated to observe, track, or regularly check another entity or process according to specified criteria or conditions.
-
B.
monitorsObligationsOf
Indicates that one entity oversees, tracks, or checks another entity’s duties or required actions to ensure they are fulfilled.
-
C.
monitoringBody
Indicates that one entity is responsible for overseeing, supervising, or tracking the activities, performance, or compliance of another entity.
-
D.
monitoredFor
Indicates that one entity is being observed or tracked over time to detect, assess, or manage the occurrence or progression of another entity (such as a condition, event, or risk).
-
E.
monitoringTarget
chosen
Indicates that one entity is being observed, tracked, or supervised by another as the focus of monitoring activities.
- 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.