Triple
T29050403
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Asgardian Royal Family |
E735249
|
entity |
| Predicate | notableStorylineContext |
P39504
|
FINISHED |
| Object | Ragnarok |
E73327
|
NE 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: Ragnarok | Statement: [Asgardian Royal Family, notableStorylineContext, Ragnarok]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: notableStorylineContext Context triple: [Asgardian Royal Family, notableStorylineContext, Ragnarok]
-
A.
notableRecentStoryline
Indicates that there is a particularly significant or newsworthy recent sequence of events or developments involving the subject.
-
B.
notableStoryArc
chosen
Indicates that there exists a significant or prominent narrative storyline or plot development involving the subject.
-
C.
notableStory
Indicates that an entity is the subject or source of a story, account, or narrative that is considered notable or significant.
-
D.
notableFeatureInStory
Indicates that a particular feature, element, or characteristic plays a significant or prominent role within a story.
-
E.
notableStorySubject
Indicates that the subject is a prominent or central topic, character, or element within a particular story or narrative.
- F. None of above.
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_69f077e64b88819094d37bdbca8191b3 |
completed | April 28, 2026, 9:03 a.m. |
| NER | Named-entity recognition | batch_6a020ab9630c8190a55efd5704cc6043 |
completed | May 11, 2026, 4:58 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a251f75b2908190b3d7cad0f81e4f76 |
completed | June 7, 2026, 7:36 a.m. |
| PD | Predicate disambiguation | batch_6a020800e2b88190a1a37e710d8c92bf |
completed | May 11, 2026, 4:46 p.m. |
Created at: April 28, 2026, 10:08 a.m.