Triple
T20935659
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Charlie |
E515576
|
entity |
| Predicate | childNarrativeRole |
P101050
|
FINISHED |
| Object | humanity's last hope |
—
|
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: humanity's last hope | Statement: [Charlie, childNarrativeRole, humanity's last hope]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: childNarrativeRole Context triple: [Charlie, childNarrativeRole, humanity's last hope]
-
A.
childInStory
Indicates that one entity is a child character who appears within the narrative context of the other entity (a story).
-
B.
roleInStories
Indicates the specific function, position, or character part an entity plays within one or more stories.
-
C.
inNarrativeRole
chosen
Indicates that one entity participates in relation to another by occupying a specific narrative function or role within a story or discourse.
-
D.
childCharacter
Indicates that one entity is a child version or child role of another character entity.
-
E.
narratorRole
Indicates that one entity serves as the narrator of another entity (such as a story, text, or media work), specifying the narrative role or function it performs.
- 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_69e0b4fc13408190b06868df03c5c29b |
completed | April 16, 2026, 10:07 a.m. |
| NER | Named-entity recognition | batch_69e6f950d5e081908ec0df4824cf69f7 |
completed | April 21, 2026, 4:13 a.m. |
| PD | Predicate disambiguation | batch_69e5c9af1fe08190953366a466950140 |
completed | April 20, 2026, 6:37 a.m. |
Created at: April 16, 2026, 12:49 p.m.