Triple
T10329768
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Acid2 |
E242844
|
entity |
| Predicate | failureIndication |
P90111
|
FINISHED |
| Object | distorted or broken face image |
—
|
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: distorted or broken face image | Statement: [Acid2, failureIndication, distorted or broken face image]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: failureIndication Context triple: [Acid2, failureIndication, distorted or broken face image]
-
A.
failureCause
Indicates that one event, condition, or factor is the reason or source that caused a particular failure to occur.
-
B.
failureEvent
chosen
Indicates that an action, process, or system has not achieved its intended outcome, resulting in a failure occurrence.
-
C.
failedOn
Indicates that an attempted action or process did not succeed when applied to a specific target, condition, or step.
-
D.
failureBehavior
Indicates how a system, component, or process is expected to respond or act when a failure or error condition occurs.
-
E.
missionFailure
Indicates that an attempted mission or operation did not achieve its intended objectives or outcome.
- 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_69d381af787481908bc401325c760a88 |
completed | April 6, 2026, 9:49 a.m. |
| NER | Named-entity recognition | batch_69d4d7cfd54c8190b6f88598339536d1 |
completed | April 7, 2026, 10:09 a.m. |
| PD | Predicate disambiguation | batch_69d4d1f760e88190abea6dcc4f04f2c1 |
completed | April 7, 2026, 9:44 a.m. |
Created at: April 6, 2026, 11:52 a.m.