Triple
T28977923
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Topthorn |
E734462
|
entity |
| Predicate | hasFateInStory |
P180515
|
FINISHED |
| Object | dies during the war |
—
|
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: dies during the war | Statement: [Topthorn, hasFateInStory, dies during the war]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasFateInStory Context triple: [Topthorn, hasFateInStory, dies during the war]
-
A.
hasAllyInStory
Indicates that one entity is portrayed as an ally or supportive partner of another entity within the context of a specific story or narrative.
-
B.
hasDifferentFateOfCharacter
Indicates that two characters experience distinct outcomes or destinies within a narrative or scenario.
-
C.
hasLeaderInStory
Indicates that one entity serves as the leader of another entity within the context of a specific story or narrative.
-
D.
hasFandomWithinStory
Indicates that within the narrative of a story, one entity is a fan or admirer of another entity (such as a character, group, or work) that exists inside that same story world.
-
E.
hasUncertainFate
Indicates that the outcome, status, or future of the related entity or event is unknown, unresolved, or not clearly determined.
- 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_69f05b0d1e7c819092baab93d3fe277e |
completed | April 28, 2026, 7 a.m. |
| NER | Named-entity recognition | batch_69f7431c0eec81909ead443e07d75e18 |
completed | May 3, 2026, 12:44 p.m. |
| PD | Predicate disambiguation | batch_69f74143cf708190a12d487884298437 |
completed | May 3, 2026, 12:36 p.m. |
| PDg | Predicate description generation | batch_69f7431aac148190bb6aac59817c174a |
completed | May 3, 2026, 12:44 p.m. |
Created at: April 28, 2026, 9:09 a.m.