Triple
T22594403
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Diné |
E574634
|
entity |
| Predicate | hasConstitutionalGovernment |
P137747
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [Diné, hasConstitutionalGovernment, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasConstitutionalGovernment Context triple: [Diné, hasConstitutionalGovernment, true]
-
A.
hasConstitutionalInstrument
Indicates that one entity is formally established, governed, or defined by a specific constitutional or foundational legal instrument.
-
B.
hasFormOfGovernmentContext
Indicates that an entity has a particular form of government specifically within a given contextual scope (such as a time period, jurisdiction, or situation).
-
C.
hasFormedGovernmentType
chosen
Indicates that an entity has established or adopted a particular type or system of government.
-
D.
hasConstitutionalStatus
Indicates that an entity possesses a particular status, role, or recognition as defined or protected by a constitution or constitutional framework.
-
E.
hasConsolidatedGovernmentWith
Indicates that two or more previously separate governmental entities have been merged into a single, unified government structure.
- 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_69e245bc11308190b69d794d5d1e0bb6 |
completed | April 17, 2026, 2:37 p.m. |
| NER | Named-entity recognition | batch_69f16164d690819096f7c4efb6cedad9 |
completed | April 29, 2026, 1:39 a.m. |
| PD | Predicate disambiguation | batch_69ee627be4248190889a88764624e174 |
completed | April 26, 2026, 7:07 p.m. |
Created at: April 17, 2026, 2:49 p.m.