Triple
T15089506
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ute Mountain Ute Tribe |
E360377
|
entity |
| Predicate | hasSchoolServices |
P33631
|
FINISHED |
| Object | tribal education programs |
—
|
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: tribal education programs | Statement: [Ute Mountain Ute Tribe, hasSchoolServices, tribal education programs]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasSchoolServices Context triple: [Ute Mountain Ute Tribe, hasSchoolServices, tribal education programs]
-
A.
hasSchoolsAccess
Indicates that one entity has permission or the ability to access schools or school-related resources associated with another entity.
-
B.
hasStudentServices
chosen
Indicates that an entity provides or is associated with student support services for another entity or group.
-
C.
hasEducationalServiceArea
Indicates that an entity (such as an educational institution or authority) is responsible for providing educational services within a specified geographic area.
-
D.
hasSchool
Indicates that an entity possesses, is associated with, or is served by a particular school.
-
E.
hasSchoolIn
Indicates that a school is located within or operates in a specified place or region.
- 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_69d85a035aa88190b52a139d3a1b7b6d |
completed | April 10, 2026, 2:01 a.m. |
| NER | Named-entity recognition | batch_69e00277ea808190be3f002a8316eff1 |
completed | April 15, 2026, 9:26 p.m. |
| PD | Predicate disambiguation | batch_69deb9645b9c8190a5712456dbd78029 |
completed | April 14, 2026, 10:02 p.m. |
Created at: April 10, 2026, 3:04 a.m.