Triple
T23677156
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Virgin of Socavón |
E584908
|
entity |
| Predicate | roleInCarnivalOfOruro |
P27714
|
FINISHED |
| Object | central religious figure |
—
|
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: central religious figure | Statement: [Virgin of Socavón, roleInCarnivalOfOruro, central religious figure]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: roleInCarnivalOfOruro Context triple: [Virgin of Socavón, roleInCarnivalOfOruro, central religious figure]
-
A.
roleInRitual
chosen
Indicates the specific function, position, or responsibility an entity holds within a particular ritual or ceremonial activity.
-
B.
roleInPeru
Indicates that an entity holds or has held an official or notable role, position, or function within the country of Peru.
-
C.
roleInMacondo
Indicates the specific function, position, or significance an entity holds within the context of Macondo.
-
D.
roleInCoco
Indicates that an entity serves a specific role or function within the context of the COCO dataset or framework.
-
E.
roleInBolivia
Indicates that an entity holds or has held an official role, position, or function within the country of Bolivia.
- 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_69e24901f7c08190909fd727632e823d |
completed | April 17, 2026, 2:51 p.m. |
| NER | Named-entity recognition | batch_69f1b4f4d4388190a0e439f4df7a0f23 |
completed | April 29, 2026, 7:36 a.m. |
| PD | Predicate disambiguation | batch_69f118dd13008190a8799b4e9cadbd79 |
completed | April 28, 2026, 8:30 p.m. |
Created at: April 17, 2026, 6:51 p.m.