Triple
T29322000
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Duel on Mustafar |
E743538
|
entity |
| Predicate | hasOutcomeForCharacter |
P33358
|
FINISHED |
| Object | Obi-Wan Kenobi goes into exile |
—
|
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: Obi-Wan Kenobi goes into exile | Statement: [Duel on Mustafar, hasOutcomeForCharacter, Obi-Wan Kenobi goes into exile]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasOutcomeForCharacter Context triple: [Duel on Mustafar, hasOutcomeForCharacter, Obi-Wan Kenobi goes into exile]
-
A.
hasEventOutcome
chosen
Indicates that a particular event results in, leads to, or is associated with a specific outcome.
-
B.
hasOutcomeDeterminedBy
Indicates that the result or consequence of one entity is decided, controlled, or directly influenced by another entity.
-
C.
hasOutcomeClass
Indicates that something is associated with a particular category or type of outcome.
-
D.
hasOutcomeIndicator
Indicates that something is associated with a specific measure or indicator used to evaluate its outcome or results.
-
E.
hasNarrativeOutcome
Indicates that an event, action, or narrative element leads to or results in a particular story-related consequence or resolution.
- 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_69f09125f784819080f4e9fce9fe624f |
completed | April 28, 2026, 10:51 a.m. |
| NER | Named-entity recognition | batch_69f6a8df16a88190a23820e64a3b1f92 |
completed | May 3, 2026, 1:46 a.m. |
| PD | Predicate disambiguation | batch_69f6a751d5e48190a77dcecbe7ef9f0b |
completed | May 3, 2026, 1:39 a.m. |
Created at: April 28, 2026, 1:23 p.m.