Triple
T11067929
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Hopi katsina dolls |
E261671
|
entity |
| Predicate | traditionalUseContext |
P66752
|
FINISHED |
| Object | Pueblo ceremonial life |
—
|
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: Pueblo ceremonial life | Statement: [Hopi katsina dolls, traditionalUseContext, Pueblo ceremonial life]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: traditionalUseContext Context triple: [Hopi katsina dolls, traditionalUseContext, Pueblo ceremonial life]
-
A.
traditionalUse
Indicates that something is used or practiced according to long-established customs, habits, or cultural traditions.
-
B.
traditionalUseDomain
chosen
Indicates that something is traditionally used or applied within a particular domain, field, or area of practice.
-
C.
contextType
Indicates the type or category of contextual information associated with an entity or event.
-
D.
hasTypicalUseContext
Indicates that something is commonly or characteristically used within a particular situation, setting, or context.
-
E.
canonicalContext
Indicates the standard or primary contextual framework within which an entity, statement, or resource is to be interpreted.
- 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_69d6aa9983c08190b0ef61603b69feac |
completed | April 8, 2026, 7:20 p.m. |
| NER | Named-entity recognition | batch_69d7992164d88190a01ed567b2529227 |
completed | April 9, 2026, 12:18 p.m. |
| PD | Predicate disambiguation | batch_69d74411d9e881908c0eeafa0f38e4b6 |
completed | April 9, 2026, 6:15 a.m. |
Created at: April 8, 2026, 9:26 p.m.