Triple
T6735687
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Pueblo peoples |
E153747
|
entity |
| Predicate | traditionalStructure |
P72652
|
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: [Pueblo peoples, traditionalStructure, kiva]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: traditionalStructure Context triple: [Pueblo peoples, traditionalStructure, kiva]
-
A.
traditionalStyle
Indicates that something follows or embodies a conventional, long-established way of doing, making, or presenting it, in contrast to modern or innovative styles.
-
B.
traditionalBase
Indicates that one entity serves as the customary or historically established foundation or basis for another.
-
C.
traditionalView
Indicates that one entity holds or represents a conventional, long-established perspective or interpretation about another entity or topic.
-
D.
traditionalEnd
Indicates that one entity is the customary or historically established conclusion, outcome, or final stage of another entity or process.
-
E.
traditionalCode
Indicates that something adheres to or is characterized by long-established, customary, or historically rooted practices, methods, or norms.
- F. None of above. chosen
Provenance (4 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_69c6880bdd68819097de8b6099992682 |
completed | March 27, 2026, 1:37 p.m. |
| NER | Named-entity recognition | batch_69c6d18369d88190a73349075462202b |
completed | March 27, 2026, 6:50 p.m. |
| PD | Predicate disambiguation | batch_69c6d09067a0819087ed6c820f4699f8 |
completed | March 27, 2026, 6:46 p.m. |
| PDg | Predicate description generation | batch_69c6d14e18d481908aaac34897c650f1 |
completed | March 27, 2026, 6:49 p.m. |
Created at: March 27, 2026, 2:09 p.m.