Triple
T32070016
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Chaudière Island |
E818981
|
entity |
| Predicate | hasNearbyProvinceBoundary |
P131063
|
FINISHED |
| Object | Ontario–Quebec border |
—
|
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: Ontario–Quebec border | Statement: [Chaudière Island, hasNearbyProvinceBoundary, Ontario–Quebec border]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasNearbyProvinceBoundary Context triple: [Chaudière Island, hasNearbyProvinceBoundary, Ontario–Quebec border]
-
A.
hasNearbyProvince
Indicates that one province is geographically close to or directly adjacent to another province.
-
B.
hasNearbyBoundary
chosen
Indicates that one entity’s boundary lies close to, but does not necessarily touch or coincide with, the boundary of another entity.
-
C.
hasNearbyCountyBorder
Indicates that the borders of two counties are geographically close to each other, though not necessarily directly adjacent.
-
D.
hasNearbyBoroughBorder
Indicates that the border of one borough is geographically close to the border of another borough.
-
E.
nearInternationalBoundary
Indicates that one entity is located close to an international boundary separating two or more countries.
- 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_69f348fecc088190af1470afe5a969f0 |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_69ff21cbd9108190a52c0ba42004c669 |
completed | May 9, 2026, noon |
| PD | Predicate disambiguation | batch_69ff1faea91881908c626c70bca5100a |
completed | May 9, 2026, 11:51 a.m. |
Created at: May 1, 2026, 12:23 a.m.