Triple
T28616516
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | ChooseFont |
E724284
|
entity |
| Predicate | indicatesFailure |
P113077
|
FINISHED |
| Object | zero return value |
—
|
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: zero return value | Statement: [ChooseFont, indicatesFailure, zero return value]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: indicatesFailure Context triple: [ChooseFont, indicatesFailure, zero return value]
-
A.
failsTo
chosen
Indicates that an expected action, process, or condition does not successfully occur or is not fulfilled.
-
B.
failedOn
Indicates that an attempted action or process did not succeed when applied to a specific target, condition, or step.
-
C.
supportsFailure
Indicates that one entity provides assistance, resources, or backing to another entity specifically in situations of error, malfunction, or unsuccessful outcomes.
-
D.
typeOfFailure
Indicates the specific kind or category of failure that occurred in relation to an entity or process.
-
E.
failureCause
Indicates that one event, condition, or factor is the reason or source that caused a particular failure to occur.
- 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_69f01d816d7c8190a1fe27e3434041dc |
completed | April 28, 2026, 2:37 a.m. |
| NER | Named-entity recognition | batch_69f6691f5e188190b12c7b2eb729a45e |
completed | May 2, 2026, 9:14 p.m. |
| PD | Predicate disambiguation | batch_69f6659b62fc8190b21555d0ba54db2d |
completed | May 2, 2026, 8:59 p.m. |
Created at: April 28, 2026, 4:32 a.m.