Triple
T12595881
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Sué |
E300728
|
entity |
| Predicate | locatedInBeliefSystem |
P75388
|
FINISHED |
| Object | Andean indigenous religions |
—
|
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: Andean indigenous religions | Statement: [Sué, locatedInBeliefSystem, Andean indigenous religions]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: locatedInBeliefSystem Context triple: [Sué, locatedInBeliefSystem, Andean indigenous religions]
-
A.
originBelief
Indicates a belief or assumption about where something or someone comes from or originated.
-
B.
positionInReligion
Indicates the specific role, rank, or office an entity holds within a religious organization or tradition.
-
C.
hasCentralBelief
Indicates that a particular belief is a core or foundational belief within an entity’s overall belief system.
-
D.
regionOfBelief
chosen
Indicates a spatial or conceptual area within which a particular belief, assumption, or proposition is considered to hold true.
-
E.
basedOnBelief
Indicates that one entity’s action, decision, or assertion is grounded in, motivated by, or derived from a particular belief held by that entity.
- 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_69d7bdea2ca881908f379526c13b1145 |
completed | April 9, 2026, 2:55 p.m. |
| NER | Named-entity recognition | batch_69d954e6e20481908bca684c4b497c48 |
completed | April 10, 2026, 7:52 p.m. |
| PD | Predicate disambiguation | batch_69d95416cbd88190b2c65196162349bc |
completed | April 10, 2026, 7:48 p.m. |
Created at: April 9, 2026, 5:08 p.m.