Triple
T2039295
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Mogollon culture |
E44703
|
entity |
| Predicate | usedStructure |
P35482
|
FINISHED |
| Object | kivas in some communities |
—
|
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: kivas in some communities | Statement: [Mogollon culture, usedStructure, kivas in some communities]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: usedStructure Context triple: [Mogollon culture, usedStructure, kivas in some communities]
-
A.
usedInStructure
Indicates that something (such as a material, component, or element) is employed as part of the composition or construction of a larger structure.
-
B.
convertedStructureUse
Indicates that an entity’s original structural use has been changed to a different use or function.
-
C.
currentStructure
Indicates that an entity is the present or active structural configuration or organization associated with another entity.
-
D.
viaStructure
Indicates that one entity is connected to or accessed through a particular structural element or medium.
-
E.
replacedStructure
Indicates that one structure has been substituted for, or taken the place of, another structure.
- 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_69a889159ec481908f9e4472d9f480c7 |
completed | March 4, 2026, 7:33 p.m. |
| NER | Named-entity recognition | batch_69abb951870481909dbdd8fc8b0c02fe |
completed | March 7, 2026, 5:36 a.m. |
| PD | Predicate disambiguation | batch_69abb7a8125881909c0cb58b777c1faa |
completed | March 7, 2026, 5:29 a.m. |
| PDg | Predicate description generation | batch_69abb90ec7948190bbfb0329e9e67cca |
completed | March 7, 2026, 5:35 a.m. |
Created at: March 4, 2026, 7:39 p.m.