Triple
T35808623
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | The Legend Killer |
E1035167
|
entity |
| Predicate | involvesStoryElement |
P35676
|
FINISHED |
| Object | ending careers of legends |
—
|
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: ending careers of legends | Statement: [The Legend Killer, involvesStoryElement, ending careers of legends]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: involvesStoryElement Context triple: [The Legend Killer, involvesStoryElement, ending careers of legends]
-
A.
storyElement
chosen
Indicates that one entity functions as a narrative component or part within the structure of another entity’s story.
-
B.
fieldInStory
Indicates that a particular field or attribute appears within, or is defined as part of, a given story.
-
C.
associatedWithPersonInStory
Indicates that one entity has a connection or involvement with a specific person within the context of a story.
-
D.
stakesInStory
Indicates that one entity has a personal investment, risk, or potential gain/loss tied to the outcome of another entity’s story or narrative.
-
E.
controlledByInStory
Indicates that, within the context of a specific story or narrative, one entity exercises control or authority over another.
- 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_69f76e1762408190b885a8456862e372 |
completed | May 3, 2026, 3:47 p.m. |
| NER | Named-entity recognition | batch_69fe349879848190bcd77e3cc3470458 |
completed | May 8, 2026, 7:08 p.m. |
| PD | Predicate disambiguation | batch_69fe31e3cf908190b23ebc2f7fe58722 |
completed | May 8, 2026, 6:56 p.m. |
Created at: May 3, 2026, 4:06 p.m.