Triple
T36299723
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Pothuraju procession |
E893473
|
entity |
| Predicate | roleOfCentralFigure |
P1183
|
FINISHED |
| Object | guardian of the goddess |
—
|
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: guardian of the goddess | Statement: [Pothuraju procession, roleOfCentralFigure, guardian of the goddess]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: roleOfCentralFigure Context triple: [Pothuraju procession, roleOfCentralFigure, guardian of the goddess]
-
A.
hasCentralFigure
chosen
Indicates that something features a primary or most important figure at its core or focus.
-
B.
biblicalFigureRole
Indicates the specific role, function, or office that a biblical figure holds within a biblical narrative or tradition.
-
C.
roleOfCharacter
Indicates that one entity serves as the narrative or functional role played by a character within a story, scenario, or context.
-
D.
roleInTheWay
Indicates that one entity is obstructing, hindering, or otherwise blocking another entity’s progress, action, or intended path.
-
E.
roleForProtagonist
Indicates the specific narrative or functional role that an entity plays in relation to the story’s main protagonist.
- 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_69f76e4a61f0819084a2b68dbbb4efc6 |
completed | May 3, 2026, 3:48 p.m. |
| NER | Named-entity recognition | batch_69fcd867f36081908c88c55a6a1404c1 |
completed | May 7, 2026, 6:22 p.m. |
| PD | Predicate disambiguation | batch_69fcd1f47b188190b4cf4b4c748d9d03 |
completed | May 7, 2026, 5:55 p.m. |
Created at: May 3, 2026, 4:09 p.m.