Triple
T14443259
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Po Nagar temple complex |
E358138
|
entity |
| Predicate | hasGoddessRole |
P92870
|
FINISHED |
| Object | Po Nagar as protector of seafarers |
—
|
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: Po Nagar as protector of seafarers | Statement: [Po Nagar temple complex, hasGoddessRole, Po Nagar as protector of seafarers]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasGoddessRole Context triple: [Po Nagar temple complex, hasGoddessRole, Po Nagar as protector of seafarers]
-
A.
hasSupremeDeityRole
Indicates that an entity holds the highest divine or ultimate god role within a religious or mythological hierarchy.
-
B.
hasBelovedRole
Indicates that an entity holds a role or position that is deeply cherished or loved by another entity.
-
C.
hasRitualRoleIn
Indicates that an entity serves a specific ritual function or role within a particular ritual, ceremony, or sacred practice.
-
D.
hasGuardianDeity
Indicates that an entity is under the protection or patronage of a specific guardian deity.
-
E.
associatedGoddess
chosen
Indicates that one entity is recognized as the goddess traditionally linked or connected to another entity (such as a place, concept, or deity).
- 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_69d8279402a88190821ffa39ae15bccf |
completed | April 9, 2026, 10:26 p.m. |
| NER | Named-entity recognition | batch_69de915d28ec81909e72124e9dd67bfb |
completed | April 14, 2026, 7:11 p.m. |
| PD | Predicate disambiguation | batch_69de5c3a02fc819097373f97a260cdeb |
completed | April 14, 2026, 3:24 p.m. |
Created at: April 10, 2026, 1:19 a.m.