Triple
T37050646
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Nlaka'pamux First Nations community network |
E917039
|
entity |
| Predicate | basedOnEthnicity |
P123087
|
FINISHED |
| Object | Nlaka'pamux people |
—
|
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: Nlaka'pamux people | Statement: [Nlaka'pamux First Nations community network, basedOnEthnicity, Nlaka'pamux people]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: basedOnEthnicity Context triple: [Nlaka'pamux First Nations community network, basedOnEthnicity, Nlaka'pamux people]
-
A.
holderEthnicity
Indicates the ethnic background or group to which the holder of something (e.g., a document, account, or item) belongs.
-
B.
dedicatedToEthnicity
Indicates that something (such as a work, event, or resource) is specifically devoted or addressed to a particular ethnic group.
-
C.
hasEthnicCharacteristic
Indicates that an entity possesses or is associated with a particular ethnic characteristic or identity.
-
D.
hasEthnicScope
chosen
Indicates that something is relevant or applicable specifically to a particular ethnic group or ethnic context.
-
E.
sharesEthnicity
Indicates that two entities belong to the same ethnic group or share the same ethnic background.
- 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_69ff5803c02c81908b63067119f5e684 |
completed | May 9, 2026, 3:51 p.m. |
| PD | Predicate disambiguation | batch_69ff576d8b308190b49a1e072a0ae661 |
completed | May 9, 2026, 3:49 p.m. |
Created at: May 3, 2026, 4:14 p.m.