Triple
T20052648
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Zia Pueblo |
E499241
|
entity |
| Predicate | hasSacredDirections |
P124196
|
FINISHED |
| Object | four cardinal directions |
—
|
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: four cardinal directions | Statement: [Zia Pueblo, hasSacredDirections, four cardinal directions]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasSacredDirections Context triple: [Zia Pueblo, hasSacredDirections, four cardinal directions]
-
A.
sacredDirection
chosen
Indicates a directional relationship that is regarded as holy, spiritually significant, or ritually privileged within a religious or cultural context.
-
B.
hasSacredSymbol
Indicates that one entity serves as a sacred or religiously significant symbol associated with another entity.
-
C.
sacredTo
Indicates that one entity is regarded as holy, revered, or dedicated in honor of another entity, such as a deity, person, or concept.
-
D.
hasSacredSpring
Indicates that one entity possesses, contains, or is associated with a spring regarded as sacred or holy.
-
E.
hasSacredNarrative
Indicates that one entity possesses, contains, or is associated with a sacred or religiously significant narrative related to another 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_69da6276bcf48190aabbf279192a5fb4 |
completed | April 11, 2026, 3:02 p.m. |
| NER | Named-entity recognition | batch_69e6633043a481908359ad232607182a |
completed | April 20, 2026, 5:32 p.m. |
| PD | Predicate disambiguation | batch_69e54cee7a5c819084ae4ff26419833f |
completed | April 19, 2026, 9:45 p.m. |
Created at: April 11, 2026, 3:38 p.m.