Triple
T32762633
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Wadsworth |
E837798
|
entity |
| Predicate | hasMultipleEndingsInNarrative |
P55743
|
FINISHED |
| Object | yes |
—
|
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: yes | Statement: [Wadsworth, hasMultipleEndingsInNarrative, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasMultipleEndingsInNarrative Context triple: [Wadsworth, hasMultipleEndingsInNarrative, yes]
-
A.
hasAmbiguousEnding
Indicates that the event, story, or situation concludes in a way that is open to multiple interpretations or lacks a clear, definitive resolution.
-
B.
hasUnfinishedEnding
Indicates that an entity concludes in an incomplete, unresolved, or open-ended manner rather than reaching a fully finished state.
-
C.
hasTragicEnding
Indicates that the event, story, or situation concludes with a sorrowful, disastrous, or otherwise deeply unfortunate outcome.
-
D.
hasEpilogueBy
Indicates that an epilogue of a work is authored, written, or created by a specified agent.
-
E.
alternateEnding
chosen
Indicates that one version of a work provides a different conclusion or final sequence of events compared to the original or primary ending.
- 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_69f34939857c8190aa9970c51feec1eb |
completed | April 30, 2026, 12:21 p.m. |
| NER | Named-entity recognition | batch_69fd592e48cc81909d754cc6c4bd99ae |
completed | May 8, 2026, 3:31 a.m. |
| PD | Predicate disambiguation | batch_69fd58b7f9b881909dc099b28d567784 |
completed | May 8, 2026, 3:30 a.m. |
Created at: May 1, 2026, 1:13 a.m.