Triple
T31536312
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ontario–Ohio border |
E804609
|
entity |
| Predicate | adjacentToUSState |
P68114
|
FINISHED |
| Object | Ohio |
—
|
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: Ohio | Statement: [Ontario–Ohio border, adjacentToUSState, Ohio]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: adjacentToUSState Context triple: [Ontario–Ohio border, adjacentToUSState, Ohio]
-
A.
nearestMainlandState
Indicates the relationship where a given location is associated with the closest U.S. mainland state in terms of geographic proximity.
-
B.
geographicallyAdjacentTo
chosen
Indicates that two geographic entities share a common boundary or are directly next to each other in space.
-
C.
hasNeighboringStateToWest
Indicates that one state is geographically located directly to the west of another state, sharing a common border.
-
D.
borderingCountryOfState
Indicates that one country shares a land or maritime boundary directly with the specified state.
-
E.
nearestStateOrTerritory
Indicates that one location is the closest state or territory to another location, typically in terms of geographic distance.
- 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_69f348d03ef88190a2b73d7b94b9e02d |
completed | April 30, 2026, 12:19 p.m. |
| NER | Named-entity recognition | batch_69f7431c0eec81909ead443e07d75e18 |
completed | May 3, 2026, 12:44 p.m. |
| PD | Predicate disambiguation | batch_69f74143cf708190a12d487884298437 |
completed | May 3, 2026, 12:36 p.m. |
Created at: April 30, 2026, 10:04 p.m.