Triple
T29185753
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Herbie |
E739863
|
entity |
| Predicate | characterOutcome |
P101514
|
FINISHED |
| Object | mental breakdown due to logical contradiction |
—
|
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: mental breakdown due to logical contradiction | Statement: [Herbie, characterOutcome, mental breakdown due to logical contradiction]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: characterOutcome Context triple: [Herbie, characterOutcome, mental breakdown due to logical contradiction]
-
A.
characterArcOutcome
chosen
Indicates the resulting change, resolution, or final state of a character’s personal journey or development over the course of a narrative.
-
B.
outcomeOf
Indicates that one entity is the result, consequence, or product that arises from another entity, event, or process.
-
C.
fictionalOutcome
Indicates that an event, action, or situation leads to a result that occurs only within a fictional, imagined, or non-real context.
-
D.
hasDifferentFateOfCharacter
Indicates that two characters experience distinct outcomes or destinies within a narrative or scenario.
-
E.
eventualFate
Indicates the ultimate outcome or final state that an entity is destined to reach over time.
- 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_69f07cb74c2c8190ad396487fcb4fde6 |
completed | April 28, 2026, 9:24 a.m. |
| NER | Named-entity recognition | batch_69fd4129a8848190a5002150278ac689 |
completed | May 8, 2026, 1:49 a.m. |
| PD | Predicate disambiguation | batch_69fd3e0515ec8190937c7af71ebc3875 |
completed | May 8, 2026, 1:36 a.m. |
Created at: April 28, 2026, 11:59 a.m.