Triple
T33128817
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Penelakut Island |
E847796
|
entity |
| Predicate | primaryReserveAreaOf |
P110251
|
FINISHED |
| Object | Penelakut First Nation |
E489464
|
NE 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: Penelakut First Nation | Statement: [Penelakut Island, primaryReserveAreaOf, Penelakut First Nation]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: primaryReserveAreaOf Context triple: [Penelakut Island, primaryReserveAreaOf, Penelakut First Nation]
-
A.
primaryArea
Indicates that one entity is the main or most important area, domain, or field associated with another entity.
-
B.
primarySourceArea
Indicates that something originates from, or is chiefly derived from, a specified source area.
-
C.
primaryUseArea
Indicates the main functional area or domain in which an entity is primarily used or applied.
-
D.
primaryLocationIn
Indicates that an entity’s main or most significant location is within or at the referenced place.
-
E.
isPrimaryPopulatedAreaOf
chosen
Indicates that a populated place is the main or principal inhabited area associated with a larger geographic or administrative entity.
- F. None of above.
Provenance (4 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_69f349588f088190b7c9588860f72033 |
completed | April 30, 2026, 12:21 p.m. |
| NER | Named-entity recognition | batch_6a037c894b488190bcbec2eccaff4a01 |
completed | May 12, 2026, 7:16 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a472f9bc0d88190906110416c5eccff |
completed | July 3, 2026, 3:42 a.m. |
| PD | Predicate disambiguation | batch_6a0379f338b881908e5593e45d764f4d |
completed | May 12, 2026, 7:05 p.m. |
Created at: May 1, 2026, 1:27 a.m.