Triple
T25088653
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ista dy Chalion |
E628391
|
entity |
| Predicate | heroicRole |
P140406
|
FINISHED |
| Object | reluctant 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: reluctant hero | Statement: [Ista dy Chalion, heroicRole, reluctant hero]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: heroicRole Context triple: [Ista dy Chalion, heroicRole, reluctant hero]
-
A.
heroClass
Indicates the character class or role that a hero belongs to within a given system or context.
-
B.
fantasyRole
Indicates that one entity holds a fictional, imaginative, or role-playing identity or function in relation to another within a fantasy or make-believe context.
-
C.
roleOfCharacter
chosen
Indicates that one entity serves as the narrative or functional role played by a character within a story, scenario, or context.
-
D.
roleOfWillChampion
Indicates that one entity is the specific role, position, or function held by Will Champion in relation to another entity.
-
E.
mythologicalRole
Indicates the specific function, duty, or status an entity holds within a mythological or legendary 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_69e2ff2f58e881908340527bc5d34f07 |
completed | April 18, 2026, 3:49 a.m. |
| NER | Named-entity recognition | batch_69f461e7fe048190adfaf71724f707e3 |
completed | May 1, 2026, 8:18 a.m. |
| PD | Predicate disambiguation | batch_69f442c861188190967655c6d8012380 |
completed | May 1, 2026, 6:06 a.m. |
Created at: April 18, 2026, 6:24 a.m.