Triple
T23491035
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Broadmoor |
E570672
|
entity |
| Predicate | inCanadianProvince |
P152583
|
FINISHED |
| Object | British Columbia |
—
|
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: British Columbia | Statement: [Broadmoor, inCanadianProvince, British Columbia]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: inCanadianProvince Context triple: [Broadmoor, inCanadianProvince, British Columbia]
-
A.
usedInCanadianProvince
Indicates that something is utilized, applied, or in operation within the jurisdiction of a Canadian province.
-
B.
currentProvinceOfTerritory
Indicates that a given province is the one that currently has administrative authority over a specified territory.
-
C.
exportProvince
Indicates the province from which goods, services, or resources are exported.
-
D.
separatesCanadianProvince
Indicates that one entity serves as a dividing boundary between a specified Canadian province and another geographic area.
-
E.
bordersCanadianProvinceIndirectlyAcrossWater
Indicates that one region is separated from a Canadian province only by a body of water, such that they face each other across water rather than sharing a direct land border.
- F. None of above. chosen
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_69e245b0b01481908f636939bedd804c |
completed | April 17, 2026, 2:37 p.m. |
| NER | Named-entity recognition | batch_69f1a7dc631c819099027e3a1c755a66 |
completed | April 29, 2026, 6:40 a.m. |
| PD | Predicate disambiguation | batch_69f0620ac3608190b36916261ea50f54 |
completed | April 28, 2026, 7:30 a.m. |
| PDg | Predicate description generation | batch_69f0bd4a0e408190ad8916faf23562d9 |
completed | April 28, 2026, 1:59 p.m. |
Created at: April 17, 2026, 6:04 p.m.