Triple
T31536313
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ontario–Ohio border |
E804609
|
entity |
| Predicate | adjacentToCanadianProvince |
P180655
|
FINISHED |
| Object | Ontario |
—
|
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 | Statement: [Ontario–Ohio border, adjacentToCanadianProvince, Ontario]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: adjacentToCanadianProvince Context triple: [Ontario–Ohio border, adjacentToCanadianProvince, Ontario]
-
A.
adjacentCanadianProvince
Indicates that two entities are Canadian provinces that share a common land or maritime border.
-
B.
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.
-
C.
adjacentProvince
Indicates that two provinces share a common boundary and are directly next to each other geographically.
-
D.
inCanadianProvince
Indicates that one entity is located within, or is a part of, a specified Canadian province.
-
E.
isWesternmostProvinceOf
Indicates that a province is the geographically furthest west among all provinces within a specified country or region.
- 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_69f348d03ef88190a2b73d7b94b9e02d |
completed | April 30, 2026, 12:19 p.m. |
| NER | Named-entity recognition | batch_69f7465687bc8190a9da44d62b634ed7 |
completed | May 3, 2026, 12:57 p.m. |
| PD | Predicate disambiguation | batch_69f743f4ceb08190a21fe7f4a99b166b |
completed | May 3, 2026, 12:47 p.m. |
| PDg | Predicate description generation | batch_69f74654c09c819084879162eba9d641 |
completed | May 3, 2026, 12:57 p.m. |
Created at: April 30, 2026, 10:04 p.m.