Triple
T30590991
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Lummi Reservation |
E778652
|
entity |
| Predicate | hasTribalSchool |
P115183
|
FINISHED |
| Object | Lummi Nation School |
—
|
NE NERFINISHED |
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: Lummi Nation School | Statement: [Lummi Reservation, hasTribalSchool, Lummi Nation School]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasTribalSchool Context triple: [Lummi Reservation, hasTribalSchool, Lummi Nation School]
-
A.
hasTribalSchoolSystem
chosen
Indicates that an entity possesses or is served by a school system operated or governed by a tribal authority.
-
B.
hasTribalInstitution
Indicates that an entity possesses, is associated with, or hosts a tribal institution (such as a tribal government, organization, or culturally recognized tribal body).
-
C.
hasSchoolIn
Indicates that a school is located within or operates in a specified place or region.
-
D.
containsNativeAmericanTribe
Indicates that one entity geographically or administratively includes the presence, territory, or jurisdiction of a Native American tribe.
-
E.
hasRegionalSchool
Indicates that an entity has an associated school that serves or operates within a specific geographic 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_69f224a1570c8190a85d3ac330479a79 |
completed | April 29, 2026, 3:32 p.m. |
| NER | Named-entity recognition | batch_69fe8ddf70e48190a917eb9e8f7b6966 |
completed | May 9, 2026, 1:29 a.m. |
| PD | Predicate disambiguation | batch_69fe87ef94dc81909bb00ec8d6de9bcd |
completed | May 9, 2026, 1:03 a.m. |
Created at: April 29, 2026, 8:24 p.m.