Triple
T3287799
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | The Mage |
E69024
|
entity |
| Predicate | supportsProtagonistIn |
P7748
|
FINISHED |
| Object | fulfilling destiny |
—
|
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: fulfilling destiny | Statement: [The Mage, supportsProtagonistIn, fulfilling destiny]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: supportsProtagonistIn Context triple: [The Mage, supportsProtagonistIn, fulfilling destiny]
-
A.
supportingCharacter
chosen
Indicates that one entity plays a secondary or assisting role in the story or context relative to another primary entity.
-
B.
protagonistIs
Indicates that one entity serves as the main character or central figure in relation to another entity or narrative context.
-
C.
supportsNarrativeOf
Indicates that one entity provides evidence, context, or structure that upholds, reinforces, or advances the storyline or interpretive account expressed by another entity.
-
D.
hasProtagonist
Indicates that a work of narrative has a main character who serves as its central focus or driving agent.
-
E.
coProtagonist
Indicates that two or more entities share the primary leading role together in the same narrative work.
- 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_69ad859d45748190b0742408c954b39f |
completed | March 8, 2026, 2:20 p.m. |
| NER | Named-entity recognition | batch_69adb058e00881908fdf0a23208860d4 |
completed | March 8, 2026, 5:22 p.m. |
| PD | Predicate disambiguation | batch_69ada421fadc8190b7c7d3c8afd20061 |
completed | March 8, 2026, 4:30 p.m. |
Created at: March 8, 2026, 3:10 p.m.