Triple
T26742819
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Sheshatshiu Innu First Nation |
E674311
|
entity |
| Predicate | hasSecondaryCommunity |
P90082
|
FINISHED |
| Object | Natuashish |
—
|
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: Natuashish | Statement: [Sheshatshiu Innu First Nation, hasSecondaryCommunity, Natuashish]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasSecondaryCommunity Context triple: [Sheshatshiu Innu First Nation, hasSecondaryCommunity, Natuashish]
-
A.
hasSecondary
chosen
Indicates that an entity is associated with an additional or subordinate counterpart beyond its primary one.
-
B.
hasSisterCommunity
Indicates a formal or recognized partnership relationship between two communities, often for mutual support, exchange, or collaboration.
-
C.
hasCommunityIn
Indicates that a community is present, active, or established within a specified location, platform, or context.
-
D.
hasSecondarySee
Indicates that an entity has an additional, secondary “see also” reference or cross-link to another related entity.
-
E.
hasCommunityArea
Indicates that an entity is associated with, located in, or belongs to a particular community area.
- 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_69eecda63a3881908095c47900692e65 |
completed | April 27, 2026, 2:44 a.m. |
| NER | Named-entity recognition | batch_69f7be53890081909b1d93f30a8f31c6 |
completed | May 3, 2026, 9:29 p.m. |
| PD | Predicate disambiguation | batch_69f7bccacbac8190978976324c67db28 |
completed | May 3, 2026, 9:23 p.m. |
Created at: April 27, 2026, 3:50 a.m.