Triple
T11540858
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Soap MacTavish |
E273668
|
entity |
| Predicate | characterStatusInOriginalTimeline |
P99598
|
FINISHED |
| Object | deceased |
—
|
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: deceased | Statement: [Soap MacTavish, characterStatusInOriginalTimeline, deceased]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: characterStatusInOriginalTimeline Context triple: [Soap MacTavish, characterStatusInOriginalTimeline, deceased]
-
A.
characterStatusInStory
Indicates the role or condition a character holds within the context of a specific story or narrative.
-
B.
alternateTimelineVersionAppearsIn
Indicates that an alternate-timeline version of an entity appears or is present within a specified context, such as a work, scene, or universe.
-
C.
formerCharacter
Indicates that an entity was once a character in a work or series but is no longer an active or current character.
-
D.
protagonistOriginTime
Indicates the point in time at which the protagonist first comes into existence or begins their story.
-
E.
characterOrigin
Indicates the source, background, or initial context from which a character originates.
- F. None of above. chosen
Provenance (4 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_69d6aae4dfa48190a3ab0b19a159a3c5 |
completed | April 8, 2026, 7:22 p.m. |
| NER | Named-entity recognition | batch_69d886deed5c81908e5c38156064f882 |
completed | April 10, 2026, 5:13 a.m. |
| PD | Predicate disambiguation | batch_69d80879fdb48190be6dacc8aa63c809 |
completed | April 9, 2026, 8:13 p.m. |
| PDg | Predicate description generation | batch_69d8279925e4819089210611c0d8e61a |
completed | April 9, 2026, 10:26 p.m. |
Created at: April 8, 2026, 9:37 p.m.