Triple
T16164337
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | May Day |
E392262
|
entity |
| Predicate | laterRoleInNarrative |
P27532
|
FINISHED |
| Object | sacrificial hero |
—
|
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: sacrificial hero | Statement: [May Day, laterRoleInNarrative, sacrificial hero]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: laterRoleInNarrative Context triple: [May Day, laterRoleInNarrative, sacrificial hero]
-
A.
laterPrimaryRole
chosen
Indicates that an entity assumes a specified primary role at a later time than another role or state in a sequence.
-
B.
characterFutureRole
Indicates the role or position that a character is expected or intended to assume at a later point in time.
-
C.
inNarrativeRole
Indicates that one entity participates in relation to another by occupying a specific narrative function or role within a story or discourse.
-
D.
metaNarrativeRole
Indicates the narrative function or role that one element (such as a character, voice, or device) plays in commenting on, framing, or reflecting the story itself at a meta-level.
-
E.
roleInStories
Indicates the specific function, position, or character part an entity plays within one or more stories.
- 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_69d87f1d32208190942e4e499a80c18c |
completed | April 10, 2026, 4:39 a.m. |
| NER | Named-entity recognition | batch_69e21e622ae481909f3cf25b38886d3a |
completed | April 17, 2026, 11:49 a.m. |
| PD | Predicate disambiguation | batch_69e1828abb608190a99d86bce1d77de2 |
completed | April 17, 2026, 12:44 a.m. |
Created at: April 10, 2026, 5:02 a.m.