Triple
T33565425
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | El alcalde de Zalamea |
E859744
|
entity |
| Predicate | occupationOfProtagonist |
P21567
|
FINISHED |
| Object | alcalde |
—
|
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: alcalde | Statement: [El alcalde de Zalamea, occupationOfProtagonist, alcalde]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: occupationOfProtagonist Context triple: [El alcalde de Zalamea, occupationOfProtagonist, alcalde]
-
A.
featuresProtagonistOccupation
chosen
Indicates that the work’s main character has a specified occupation or job role.
-
B.
otherProtagonistOccupation
Indicates that another main character in the narrative has a specific occupation or job role.
-
C.
protagonistSocialStatus
Indicates the social standing or class position held by the story’s main character in relation to others in their society.
-
D.
roleForProtagonist
Indicates the specific narrative or functional role that an entity plays in relation to the story’s main protagonist.
-
E.
protagonistIs
Indicates that one entity serves as the main character or central figure in relation to another entity or narrative 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_69f3497c1d288190a844ea699914e038 |
completed | April 30, 2026, 12:22 p.m. |
| NER | Named-entity recognition | batch_69f6fb19063c81909466b329655c8583 |
completed | May 3, 2026, 7:36 a.m. |
| PD | Predicate disambiguation | batch_69f6f96badb08190994442c2aba840b1 |
completed | May 3, 2026, 7:29 a.m. |
Created at: May 1, 2026, 1:40 a.m.