Triple
T19398170
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Level 3 |
E485245
|
entity |
| Predicate | fallbackResponsibility |
P84784
|
FINISHED |
| Object | automated system requests human to intervene |
—
|
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: automated system requests human to intervene | Statement: [Level 3, fallbackResponsibility, automated system requests human to intervene]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: fallbackResponsibility Context triple: [Level 3, fallbackResponsibility, automated system requests human to intervene]
-
A.
fallbackTo
Indicates that when a primary option, method, or resource is unavailable or fails, an alternative one is used instead.
-
B.
failureBehavior
chosen
Indicates how a system, component, or process is expected to respond or act when a failure or error condition occurs.
-
C.
responsibleFor
Indicates that one entity has a duty, obligation, or role to manage, oversee, or be accountable for another entity or outcome.
-
D.
reallocatedResponsibilityFrom
Indicates that responsibility for something was transferred away from one party and assigned to another.
-
E.
fallStatus
Indicates the condition or outcome of a fall event affecting an entity.
- 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.