Triple
T37782032
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Bars County |
E941854
|
entity |
| Predicate | borderedByHistoricalCounty |
P58874
|
FINISHED |
| Object | Hont County |
—
|
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: Hont County | Statement: [Bars County, borderedByHistoricalCounty, Hont County]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: borderedByHistoricalCounty Context triple: [Bars County, borderedByHistoricalCounty, Hont County]
-
A.
bordersHistoricCounty
chosen
Indicates that one historic county shares a boundary with another historic county.
-
B.
hasNearbyCountyBorder
Indicates that the borders of two counties are geographically close to each other, though not necessarily directly adjacent.
-
C.
historicalCounty
Indicates that an entity was located within or associated with a county as it existed in the past, even if that county’s boundaries or administrative status have since changed.
-
D.
borderedBy
Indicates that one entity shares a common boundary or edge with another entity.
-
E.
historicBoundaryFor
Indicates that one entity serves as a historical boundary or border associated with another entity, typically reflecting past territorial or administrative limits.
- 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_69f76ee5cb0c81909a363d1c929156c0 |
completed | May 3, 2026, 3:51 p.m. |
| NER | Named-entity recognition | batch_6a00119d821c8190874786391b27ef23 |
completed | May 10, 2026, 5:03 a.m. |
| PD | Predicate disambiguation | batch_6a001143fb6881909ac0ae8bfea04351 |
completed | May 10, 2026, 5:01 a.m. |
Created at: May 3, 2026, 4:19 p.m.