Triple
T17280978
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Sandia Pueblo |
E419525
|
entity |
| Predicate | isTribalGovernmentOf |
P126602
|
FINISHED |
| Object | Sandia Pueblo members |
—
|
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: Sandia Pueblo members | Statement: [Sandia Pueblo, isTribalGovernmentOf, Sandia Pueblo members]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isTribalGovernmentOf Context triple: [Sandia Pueblo, isTribalGovernmentOf, Sandia Pueblo members]
-
A.
associatedTribalGovernment
Indicates a relationship where an entity is formally linked or connected to a specific tribal government.
-
B.
tribalHeadquartersOf
Indicates that one location serves as the official headquarters or central administrative base for a particular tribe.
-
C.
governingTribalPresence
Indicates that an entity holds governing authority or administrative control over a tribal presence in a given area or context.
-
D.
tribalOrganization
Indicates that an entity is organized as, or formally recognized as, a tribal governing or social structure.
-
E.
indigenousGovernment
Indicates that a government is native to, and originates from, the original inhabitants of a particular region or territory.
- 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_69d886da626481908a14ce7830329a35 |
completed | April 10, 2026, 5:12 a.m. |
| NER | Named-entity recognition | batch_69e43329904c8190a4cbc856b9b94ff8 |
completed | April 19, 2026, 1:43 a.m. |
| PD | Predicate disambiguation | batch_69e3832c3b98819091967ac7e91ba316 |
completed | April 18, 2026, 1:12 p.m. |
| PDg | Predicate description generation | batch_69e3874077948190acf5706cfe917d29 |
completed | April 18, 2026, 1:29 p.m. |
Created at: April 10, 2026, 5:40 a.m.