Triple
T34588944
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Hazel |
E888122
|
entity |
| Predicate | roleInSaga |
P140406
|
FINISHED |
| Object | focus of the series’ overarching narrative |
—
|
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: focus of the series’ overarching narrative | Statement: [Hazel, roleInSaga, focus of the series’ overarching narrative]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: roleInSaga Context triple: [Hazel, roleInSaga, focus of the series’ overarching narrative]
-
A.
roleInTheWay
Indicates that one entity is obstructing, hindering, or otherwise blocking another entity’s progress, action, or intended path.
-
B.
roleInTauris
Indicates that an entity has a specific role or function within the context of Tauris (e.g., a work, setting, or domain associated with Tauris).
-
C.
roleForProtagonist
Indicates the specific narrative or functional role that an entity plays in relation to the story’s main protagonist.
-
D.
roleInTheMangler
Indicates that an entity has a specific role or involvement in the work titled "The Mangler."
-
E.
roleOfCharacter
chosen
Indicates that one entity serves as the narrative or functional role played by a character within a story, scenario, or context.
- 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_69f349d3bfcc81909874c99e646fb3ea |
completed | April 30, 2026, 12:23 p.m. |
| NER | Named-entity recognition | batch_6a00ccadb6908190ab810a7c05315fa8 |
completed | May 10, 2026, 6:21 p.m. |
| PD | Predicate disambiguation | batch_6a00cc0f86b88190a0d2c43618558f86 |
completed | May 10, 2026, 6:18 p.m. |
Created at: May 1, 2026, 2:03 a.m.