Triple
T36830598
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Blackfeet Community College |
E910126
|
entity |
| Predicate | triballyControlled |
P186339
|
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: [Blackfeet Community College, triballyControlled, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: triballyControlled Context triple: [Blackfeet Community College, triballyControlled, true]
-
A.
tribalOrganization
Indicates that an entity is organized as, or formally recognized as, a tribal governing or social structure.
-
B.
federallyRecognizedTribe
Indicates that the subject is officially acknowledged by the federal government as a Native American tribe with a recognized government-to-government relationship.
-
C.
recognizedTribalEntity
Indicates that an entity is officially acknowledged as a tribal nation or community by a governing authority.
-
D.
governingTribalPresence
Indicates that an entity holds governing authority or administrative control over a tribal presence in a given area or context.
-
E.
associatedTribalGovernment
Indicates a relationship where an entity is formally linked or connected to a specific tribal government.
- 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_69f76e7e9d60819092442fba73290a46 |
completed | May 3, 2026, 3:49 p.m. |
| NER | Named-entity recognition | batch_69f7cabdd2d88190be1c8de7e499cb83 |
completed | May 3, 2026, 10:22 p.m. |
| PD | Predicate disambiguation | batch_69f7c89b528c8190bf80b230fc7c7108 |
completed | May 3, 2026, 10:13 p.m. |
| PDg | Predicate description generation | batch_69f7ca91f1808190b2a05c4b691da0bb |
completed | May 3, 2026, 10:22 p.m. |
Created at: May 3, 2026, 4:13 p.m.