Triple
T30222607
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Kitimat Arm |
E768388
|
entity |
| Predicate | nearAdministrativeRegion |
P141258
|
FINISHED |
| Object | Regional District of Kitimat–Stikine |
—
|
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: Regional District of Kitimat–Stikine | Statement: [Kitimat Arm, nearAdministrativeRegion, Regional District of Kitimat–Stikine]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: nearAdministrativeRegion Context triple: [Kitimat Arm, nearAdministrativeRegion, Regional District of Kitimat–Stikine]
-
A.
associatedAdministrativeRegion
Indicates that an entity is linked to, or falls under the jurisdiction of, a particular administrative region.
-
B.
nearbySettlementRegion
Indicates that a settlement is located close to or within the surrounding area of a specified region.
-
C.
nearProvince
Indicates that one province is geographically close to or bordering another province.
-
D.
hasNearbyGeographicalArea
chosen
Indicates that one geographical area is located in close spatial proximity to another geographical area.
-
E.
laterAdministrativeRegion
Indicates that an entity became part of, or was replaced by, another administrative region at a later point in time.
- 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_69f2247fd8b8819087fcf83cb7a05eb8 |
completed | April 29, 2026, 3:32 p.m. |
| NER | Named-entity recognition | batch_69f6801e5eb081908d07ef701d78118b |
completed | May 2, 2026, 10:52 p.m. |
| PD | Predicate disambiguation | batch_69f6760216108190bbb708d53a6c2c25 |
completed | May 2, 2026, 10:09 p.m. |
Created at: April 29, 2026, 7:35 p.m.