Triple
T35839311
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Keres Pueblos |
E1036028
|
entity |
| Predicate | hasSacredStructure |
P170654
|
FINISHED |
| Object | kiva |
—
|
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: kiva | Statement: [Keres Pueblos, hasSacredStructure, kiva]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasSacredStructure Context triple: [Keres Pueblos, hasSacredStructure, kiva]
-
A.
hasSacredPrecinct
chosen
Indicates that an entity possesses or contains a designated sacred area or precinct associated with religious or ritual significance.
-
B.
hasSacredSymbol
Indicates that one entity serves as a sacred or religiously significant symbol associated with another entity.
-
C.
hasTempleOf
Indicates that a location or entity possesses, contains, or is the site of a temple dedicated to a particular deity, figure, or purpose.
-
D.
hasReligiousBuildingAlong
Indicates that a religious building is located along the course, path, or extent of the referenced entity.
-
E.
hasPantheonStructure
Indicates that an entity possesses or is associated with a pantheon-like hierarchical structure, typically organizing multiple deities or divine figures.
- 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_69f76e1a29e8819088280f26096aeb55 |
completed | May 3, 2026, 3:47 p.m. |
| NER | Named-entity recognition | batch_69fbad1e94988190b86d447a68e65067 |
completed | May 6, 2026, 9:05 p.m. |
| PD | Predicate disambiguation | batch_69fba881b8e0819094790935152b99a1 |
completed | May 6, 2026, 8:45 p.m. |
Created at: May 3, 2026, 4:06 p.m.