Triple
T10072690
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Salasaca people |
E213667
|
entity |
| Predicate | cosmovision |
P19063
|
FINISHED |
| Object | Andean worldview |
—
|
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 worldview | Statement: [Salasaca people, cosmovision, Andean worldview]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: cosmovision Context triple: [Salasaca people, cosmovision, Andean worldview]
-
A.
cosmologicalRealm
Indicates that one entity exists in, belongs to, or is associated with a particular cosmological realm or plane of existence relative to another.
-
B.
cosmologicalTheme
Indicates that a work, idea, or element centrally involves themes related to the origin, structure, or fundamental nature of the universe and cosmos.
-
C.
cosmicForm
Indicates a relationship where an entity manifests, assumes, or is represented in a vast, universal, or transcendent cosmic form.
-
D.
worldview
chosen
Indicates the overarching perspective or framework through which an entity interprets and understands the world and its experiences.
-
E.
cosmicFunction
Indicates a relationship where an entity serves a fundamental or overarching role within a cosmic or universal system.
- 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_69ca839add308190b57d53b4ec21f2d0 |
completed | March 30, 2026, 2:07 p.m. |
| NER | Named-entity recognition | batch_69cdd013c9d0819091ebe6fc399832de |
completed | April 2, 2026, 2:10 a.m. |
| PD | Predicate disambiguation | batch_69cd4b97870481908f7a89df10d58a9e |
completed | April 1, 2026, 4:45 p.m. |
Created at: March 30, 2026, 8:59 p.m.