Triple
T32403052
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Fuenteovejuna |
E828002
|
entity |
| Predicate | protagonistCollective |
P24067
|
FINISHED |
| Object | the villagers of Fuenteovejuna |
—
|
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: the villagers of Fuenteovejuna | Statement: [Fuenteovejuna, protagonistCollective, the villagers of Fuenteovejuna]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: protagonistCollective Context triple: [Fuenteovejuna, protagonistCollective, the villagers of Fuenteovejuna]
-
A.
coProtagonist
Indicates that two or more entities share the primary leading role together in the same narrative work.
-
B.
hasProtagonistGroup
chosen
Indicates that a narrative work features a central group of characters who collectively serve as the main protagonists.
-
C.
protagonistIs
Indicates that one entity serves as the main character or central figure in relation to another entity or narrative context.
-
D.
protagonistAllegiance
Indicates the group, cause, or side with which the main character is aligned or to which they show loyalty.
-
E.
protagonistCount
Indicates the number of primary protagonists involved in a given narrative or work.
- 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_69f34919342c8190a4c3bf35a90d4e58 |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_69f72921cf2c8190909bb53f78bcc890 |
completed | May 3, 2026, 10:53 a.m. |
| PD | Predicate disambiguation | batch_69f7283d8cec8190b524c144948bc4ec |
completed | May 3, 2026, 10:49 a.m. |
Created at: May 1, 2026, 12:53 a.m.