Triple
T37050782
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Nespelem people |
E917042
|
entity |
| Predicate | modernCommunityCenter |
P47569
|
FINISHED |
| Object | Nespelem, Washington |
—
|
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: Nespelem, Washington | Statement: [Nespelem people, modernCommunityCenter, Nespelem, Washington]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: modernCommunityCenter Context triple: [Nespelem people, modernCommunityCenter, Nespelem, Washington]
-
A.
modernCommunity
Indicates that a community exists in or reflects contemporary times, practices, or conditions rather than historical or traditional ones.
-
B.
hasCommunityCentre
chosen
Indicates that a place or area possesses or is served by a community centre facility.
-
C.
isSocialCenterOf
Indicates that one entity serves as the primary gathering place or hub for social activities and interactions for another entity or group.
-
D.
cultCenterFor
Indicates that a location serves as a primary religious or ritual center dedicated to the worship or veneration of a particular entity.
-
E.
municipalCentre
Indicates that a location functions as the primary administrative or civic center for a municipality.
- 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_69f76e94d0308190a3f06890e133c88e |
completed | May 3, 2026, 3:49 p.m. |
| NER | Named-entity recognition | batch_69fda5003cdc8190a558501271389912 |
completed | May 8, 2026, 8:55 a.m. |
| PD | Predicate disambiguation | batch_69fda05bfc2c819096821a5300e9bb24 |
completed | May 8, 2026, 8:35 a.m. |
Created at: May 3, 2026, 4:14 p.m.