Triple
T27014531
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Casey Ryback |
E680487
|
entity |
| Predicate | settingOfMainConflict |
P56733
|
FINISHED |
| Object | USS Missouri |
—
|
NE NERFINISHED |
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: USS Missouri | Statement: [Casey Ryback, settingOfMainConflict, USS Missouri]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: settingOfMainConflict Context triple: [Casey Ryback, settingOfMainConflict, USS Missouri]
-
A.
settingOfConflict
chosen
Indicates the location or context in which a conflict between entities takes place.
-
B.
storyConflict
Indicates a relationship where a story contains or centers around a central problem, opposition, or tension that drives its plot.
-
C.
mainConflict
Indicates the primary opposing force, problem, or struggle that drives tension and narrative progression between entities or sides.
-
D.
centralConflictIn
Indicates that one situation, issue, or opposition serves as the primary source of tension or struggle within another context, such as a story, event, or scenario.
-
E.
storyConflictSource
Indicates the source or cause from which a story’s central conflict arises.
- 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_69eeeb53939c8190bd431f32b060f01f |
completed | April 27, 2026, 4:51 a.m. |
| NER | Named-entity recognition | batch_69f6640168948190811bd5f933a87cf5 |
completed | May 2, 2026, 8:52 p.m. |
| PD | Predicate disambiguation | batch_69f6633451948190bcc0410602bb4914 |
completed | May 2, 2026, 8:48 p.m. |
Created at: April 27, 2026, 7:05 a.m.