Triple
T36213229
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Jackson Township, Licking County, Ohio |
E1047616
|
entity |
| Predicate | hasNeighboringTownship |
P165353
|
FINISHED |
| Object | Eden Township, Licking 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: Eden Township, Licking County, Ohio | Statement: [Jackson Township, Licking County, Ohio, hasNeighboringTownship, Eden Township, Licking County, Ohio]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasNeighboringTownship Context triple: [Jackson Township, Licking County, Ohio, hasNeighboringTownship, Eden Township, Licking County, Ohio]
-
A.
neighboringTownship
chosen
Indicates that two townships share a common boundary and are directly adjacent to each other.
-
B.
hasTownship
Indicates that one administrative area or jurisdiction includes or is associated with a specific township.
-
C.
hasNeighboringChiefdom
Indicates that one chiefdom is geographically adjacent to or directly borders another chiefdom.
-
D.
hasNeighboringSettlementInDistrict
Indicates that one settlement has another settlement as its neighbor within the same administrative district.
-
E.
neighbouringMunicipality
Indicates that one municipality directly borders and is adjacent to another municipality.
- 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_69f76e4214748190a76c986d2a1838c2 |
completed | May 3, 2026, 3:48 p.m. |
| NER | Named-entity recognition | batch_6a004c41f13c8190bc47daf6a5ca3949 |
completed | May 10, 2026, 9:13 a.m. |
| PD | Predicate disambiguation | batch_6a004bce3e3081909b35ae5b3bf2b35e |
completed | May 10, 2026, 9:11 a.m. |
Created at: May 3, 2026, 4:09 p.m.