Triple
T10339227
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Frank Burns |
E243084
|
entity |
| Predicate | inUniverseFate |
P24728
|
FINISHED |
| Object | has a nervous breakdown and is sent stateside |
—
|
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: has a nervous breakdown and is sent stateside | Statement: [Frank Burns, inUniverseFate, has a nervous breakdown and is sent stateside]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: inUniverseFate Context triple: [Frank Burns, inUniverseFate, has a nervous breakdown and is sent stateside]
-
A.
inUniverse
Indicates that one entity exists, occurs, or is set within the fictional or conceptual universe defined by another entity.
-
B.
inUniverseConsequence
Indicates that one event, action, or state leads to a resulting effect or outcome within the same fictional or defined universe.
-
C.
eraInUniverse
Indicates the specific time period or era during which something exists or occurs within a particular fictional or defined universe.
-
D.
eventualFate
chosen
Indicates the ultimate outcome or final state that an entity is destined to reach over time.
-
E.
fate
Indicates that an entity is destined or predetermined to experience a particular outcome or course of events beyond its control.
- 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_69d4e91fdb2081909866c6ecf417d75a |
completed | April 7, 2026, 11:23 a.m. |
| PD | Predicate disambiguation | batch_69d4df9dc3208190bf1bd106f44f6202 |
completed | April 7, 2026, 10:42 a.m. |
Created at: April 6, 2026, 11:54 a.m.