Triple
T6587303
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Susquehanna County |
E159256
|
entity |
| Predicate | hasBorderRelationshipWith |
P37800
|
FINISHED |
| Object | Broome County, New York |
—
|
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: Broome County, New York | Statement: [Susquehanna County, hasBorderRelationshipWith, Broome County, New York]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasBorderRelationshipWith Context triple: [Susquehanna County, hasBorderRelationshipWith, Broome County, New York]
-
A.
hasBorderRelation
chosen
Indicates that one entity shares a boundary or border with another entity.
-
B.
relatedBorder
Indicates that two geographic or political entities share a common boundary or border with each other.
-
C.
hasBorderConnection
Indicates that two regions or entities share a common boundary or are directly connected along a border.
-
D.
borderedBy
Indicates that one entity shares a common boundary or edge with another entity.
-
E.
hasBorderWithNonSovereignEntity
Indicates that one entity shares a land or maritime border with a political or territorial unit that is not fully sovereign.
- 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_69c688366ce8819083f8883983c0df92 |
completed | March 27, 2026, 1:37 p.m. |
| NER | Named-entity recognition | batch_69c6c07cdf048190945ca5810fb1de88 |
completed | March 27, 2026, 5:38 p.m. |
| PD | Predicate disambiguation | batch_69c6acfb462481909cb7aff5af4bca9d |
completed | March 27, 2026, 4:14 p.m. |
Created at: March 27, 2026, 1:55 p.m.