Triple
T30773680
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Kitimat Harbour |
E783598
|
entity |
| Predicate | locatedInBayOrChannel |
P87968
|
FINISHED |
| Object | Douglas Channel |
—
|
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: Douglas Channel | Statement: [Kitimat Harbour, locatedInBayOrChannel, Douglas Channel]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: locatedInBayOrChannel Context triple: [Kitimat Harbour, locatedInBayOrChannel, Douglas Channel]
-
A.
locatedInBayOf
Indicates that something is situated within or directly on a specific bay.
-
B.
partOfHarborOrSound
Indicates that one entity is a component, area, or feature within a harbor or sound.
-
C.
locatedInBasin
Indicates that one geographical or hydrological feature lies within the drainage or catchment area of a specified basin.
-
D.
locatedInHarbourArea
chosen
Indicates that something is situated within the geographic or administrative boundaries of a harbour area.
-
E.
bayOf
Indicates that one location is a bay that forms an inlet or coastal indentation associated with another geographic entity, such as a sea, ocean, or coastline.
- 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_69f224b1519081908b9db003fd2073e0 |
completed | April 29, 2026, 3:33 p.m. |
| NER | Named-entity recognition | batch_6a00dc330b148190aaae2ac6a5327960 |
completed | May 10, 2026, 7:27 p.m. |
| PD | Predicate disambiguation | batch_6a00d9d2904881909dafbfe7b9e5ad81 |
completed | May 10, 2026, 7:17 p.m. |
Created at: April 29, 2026, 8:40 p.m.