Triple
T36965395
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Harry Mason |
E914414
|
entity |
| Predicate | endingDependentFate |
P123327
|
FINISHED |
| Object | multiple endings |
—
|
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: multiple endings | Statement: [Harry Mason, endingDependentFate, multiple endings]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: endingDependentFate Context triple: [Harry Mason, endingDependentFate, multiple endings]
-
A.
fateDependsOn
chosen
Indicates that the outcome or destiny of one entity is determined or significantly influenced by another entity or condition.
-
B.
eventualFate
Indicates the ultimate outcome or final state that an entity is destined to reach over time.
-
C.
fate
Indicates that an entity is destined or predetermined to experience a particular outcome or course of events beyond its control.
-
D.
chosenFate
Indicates that an entity has actively selected or accepted a particular destiny or outcome, rather than having it imposed by external forces.
-
E.
hasUncertainFate
Indicates that the outcome, status, or future of the related entity or event is unknown, unresolved, or not clearly determined.
- 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_69f76e8c498c8190b2842db80aea8b3b |
completed | May 3, 2026, 3:49 p.m. |
| NER | Named-entity recognition | batch_69fa0a7b00948190a257273d9968c5d7 |
completed | May 5, 2026, 3:19 p.m. |
| PD | Predicate disambiguation | batch_69f9fec9c9488190ae2a349651a02782 |
completed | May 5, 2026, 2:29 p.m. |
Created at: May 3, 2026, 4:14 p.m.