Triple
T34981062
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | The Happy Return |
E1008814
|
entity |
| Predicate | mainProtagonistRank |
P9202
|
FINISHED |
| Object | Royal Navy captain |
—
|
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: Royal Navy captain | Statement: [The Happy Return, mainProtagonistRank, Royal Navy captain]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: mainProtagonistRank Context triple: [The Happy Return, mainProtagonistRank, Royal Navy captain]
-
A.
protagonistRank
Indicates the relative narrative importance or centrality of a character within a story, typically ranking how primary they are as a protagonist compared to others.
-
B.
mainProtagonist
chosen
Indicates that the subject is the central character or primary focus in the narrative of the related work.
-
C.
roleForProtagonist
Indicates the specific narrative or functional role that an entity plays in relation to the story’s main protagonist.
-
D.
mainMortalCharacter
Indicates that the referenced entity serves as the primary mortal (non-immortal) character in the context of a story or narrative.
-
E.
ruleOfProtagonist
Indicates that the subject holds governing authority or dominion over the protagonist.
- 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_69f76dc844a48190881951fffb83d17e |
completed | May 3, 2026, 3:46 p.m. |
| NER | Named-entity recognition | batch_69f7b2f3a104819098ddd8909eaf596c |
completed | May 3, 2026, 8:41 p.m. |
| PD | Predicate disambiguation | batch_69f7b1b8a9fc8190a1279e67a2d12707 |
completed | May 3, 2026, 8:36 p.m. |
Created at: May 3, 2026, 4:01 p.m.