Triple
T36622175
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Peter Parley |
E904071
|
entity |
| Predicate | fictionalNarratorOf |
P17514
|
FINISHED |
| Object | Peter Parley series |
—
|
NE NERFINISHED |
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: Peter Parley series | Statement: [Peter Parley, fictionalNarratorOf, Peter Parley series]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: fictionalNarratorOf Context triple: [Peter Parley, fictionalNarratorOf, Peter Parley series]
-
A.
fictionalNarrator
chosen
Indicates that one entity serves as the narrator or storytelling voice within a fictional work that features the other entity.
-
B.
narratorOf
Indicates that one entity serves as the narrator or storytelling voice for another entity, such as a text, story, or media work.
-
C.
narrativeAuthor
Indicates that one entity is the author or creator of a given narrative associated with another entity.
-
D.
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.
-
E.
narratorType
Indicates the narrative perspective or role from which a story or account is being told.
- 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_69f76e6ae750819096911e6e2d4d12c5 |
completed | May 3, 2026, 3:48 p.m. |
| NER | Named-entity recognition | batch_69ff2fbae9b48190847eefa1c227d43e |
completed | May 9, 2026, 12:59 p.m. |
| PD | Predicate disambiguation | batch_69ff2f2218048190a32224a648182b5d |
completed | May 9, 2026, 12:57 p.m. |
Created at: May 3, 2026, 4:11 p.m.