Triple
T23216246
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Tyler County, West Virginia |
E580749
|
entity |
| Predicate | hasBorderAcrossRiverWith |
P143613
|
FINISHED |
| Object | Monroe County, 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: Monroe County, Ohio | Statement: [Tyler County, West Virginia, hasBorderAcrossRiverWith, Monroe County, Ohio]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasBorderAcrossRiverWith Context triple: [Tyler County, West Virginia, hasBorderAcrossRiverWith, Monroe County, Ohio]
-
A.
borderedByCountryAcrossRiver
Indicates that one country shares a border with another country, with the boundary specifically formed or separated by a river.
-
B.
bordersAcrossRiver
chosen
Indicates that two regions or entities share a boundary with each other that is separated or defined by a river.
-
C.
crossedByRiver
Indicates that a river passes across or through a specified area, feature, or route.
-
D.
locatedAcrossRiverFrom
Indicates that one entity is situated on the opposite side of a river relative to another entity.
-
E.
hasRiverCrossingType
Indicates the type or nature of a river crossing associated with an entity (e.g., bridge, ford, ferry).
- 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_69e2460389408190be74f41d217799a9 |
completed | April 17, 2026, 2:38 p.m. |
| NER | Named-entity recognition | batch_69f19165949c81908e4d66a8a2b0a25a |
completed | April 29, 2026, 5:04 a.m. |
| PD | Predicate disambiguation | batch_69effcccee508190a7ae311fdd319806 |
completed | April 28, 2026, 12:18 a.m. |
Created at: April 17, 2026, 4:08 p.m.