Triple
T26730312
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Columbia Township, Hamilton County, Ohio |
E673951
|
entity |
| Predicate | hasNonContiguousTerritory |
P195721
|
FINISHED |
| Object | yes |
—
|
LITERAL FINISHED |
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: yes | Statement: [Columbia Township, Hamilton County, Ohio, hasNonContiguousTerritory, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasNonContiguousTerritory Context triple: [Columbia Township, Hamilton County, Ohio, hasNonContiguousTerritory, yes]
-
A.
separatesTerritoryOf
Indicates that one entity serves as a boundary or divider between the territories or domains of two other entities.
-
B.
hasAdjacentMainlandArea
Indicates that one geographic area directly borders or touches a contiguous mainland region.
-
C.
hasTerritorialContinuity
Indicates that two or more geographic areas are physically connected in an unbroken, contiguous territory without gaps or separations.
-
D.
hasOverseasTerritory
Indicates that one entity possesses or controls a territory located outside its own primary geographic or sovereign domain.
-
E.
hasConstituentTerritory
Indicates that one geopolitical entity includes another as a territorial part or subdivision within its jurisdiction.
- F. None of above. chosen
Provenance (4 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_69eecda57ab481909424e98f2835e7d8 |
completed | April 27, 2026, 2:44 a.m. |
| NER | Named-entity recognition | batch_69fde49a084081909d99b1e0258169d5 |
completed | May 8, 2026, 1:26 p.m. |
| PD | Predicate disambiguation | batch_69fde1d04bd881909a46ecbbf18dfe59 |
completed | May 8, 2026, 1:14 p.m. |
| PDg | Predicate description generation | batch_69fde49953c481909ac352ab36fa9ff2 |
completed | May 8, 2026, 1:26 p.m. |
Created at: April 27, 2026, 3:44 a.m.