Triple
T38593124
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Jack Morrison |
E932498
|
entity |
| Predicate | laterStatusInLore |
P201411
|
FINISHED |
| Object | alive |
—
|
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: alive | Statement: [Jack Morrison, laterStatusInLore, alive]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: laterStatusInLore Context triple: [Jack Morrison, laterStatusInLore, alive]
-
A.
laterStatus
Indicates that one entity represents a subsequent or resulting status or condition of another entity in time.
-
B.
laterStatusWith
chosen
Indicates that one entity represents a subsequent or updated status of another entity in time.
-
C.
laterNarrator
Indicates that the narration is provided by a narrator who speaks from a later point in time than the events being described.
-
D.
loreStatus
Indicates the canonical or contextual standing of something within a fictional or narrative universe (such as whether it is official, speculative, or non-canonical lore).
-
E.
narrativeStatus
Indicates the role or state of an element within a narrative, such as whether it is current, hypothetical, background, or otherwise positioned in the story’s progression.
- 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_69f76ec654d48190b421111cf26e54d9 |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_6a01839b071481909f9cc79a6a09387d |
completed | May 11, 2026, 7:22 a.m. |
| PD | Predicate disambiguation | batch_6a017edbed688190baa61cbae5110c8e |
completed | May 11, 2026, 7:01 a.m. |
Created at: May 3, 2026, 4:32 p.m.