Triple
T34135414
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | archpriest of Hita |
E875554
|
entity |
| Predicate | narrativeVoiceOf |
P17575
|
FINISHED |
| Object | Libro de buen amor |
—
|
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: Libro de buen amor | Statement: [archpriest of Hita, narrativeVoiceOf, Libro de buen amor]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: narrativeVoiceOf Context triple: [archpriest of Hita, narrativeVoiceOf, Libro de buen amor]
-
A.
narratorOf
chosen
Indicates that one entity serves as the narrator or storytelling voice for another entity, such as a text, story, or media work.
-
B.
narratorType
Indicates the narrative perspective or role from which a story or account is being told.
-
C.
narratesAs
Indicates that one entity tells, recounts, or presents a story, event, or information in the manner, style, or voice of another entity.
-
D.
narratorIn
Indicates that one entity serves as the narrator or storytelling voice within the context of another entity (such as a work, scene, or narrative segment).
-
E.
narratorBasedOn
Indicates that a narrative’s narrator is modeled on, inspired by, or derived from a particular real or fictional entity.
- 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_69f349aaeef08190a20e72a3fdeb7052 |
completed | April 30, 2026, 12:23 p.m. |
| NER | Named-entity recognition | batch_69fccdd496048190bca801a8a9eecb62 |
completed | May 7, 2026, 5:37 p.m. |
| PD | Predicate disambiguation | batch_69fcccee6240819084680887731ff64b |
completed | May 7, 2026, 5:33 p.m. |
Created at: May 1, 2026, 1:53 a.m.