Triple
T29718377
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Union, Ohio |
E751977
|
entity |
| Predicate | partiallyInCounty |
P178608
|
FINISHED |
| Object | Miami 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: Miami County, Ohio | Statement: [Union, Ohio, partiallyInCounty, Miami County, Ohio]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: partiallyInCounty Context triple: [Union, Ohio, partiallyInCounty, Miami County, Ohio]
-
A.
isInCountySubdivision
Indicates that one entity (typically a place or address) is located within the boundaries of a specific county subdivision.
-
B.
isOnlyInCounty
Indicates that an entity exists or occurs exclusively within a single specified county and not in any other county.
-
C.
isInCountySeatAreaOfInfluence
Indicates that one location lies within the geographic or functional area of influence of a county seat.
-
D.
includesCounty
Indicates that a larger geographic or administrative region contains or encompasses a specific county within its boundaries.
-
E.
isInCountySeatCounty
Indicates that a given place is located within the county that serves as the county seat for a specified 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_69f0d628c00c8190ab5ee7e423d7ec3c |
completed | April 28, 2026, 3:45 p.m. |
| NER | Named-entity recognition | batch_69f7117e55908190a67105e92bc4830f |
completed | May 3, 2026, 9:12 a.m. |
| PD | Predicate disambiguation | batch_69f70f380690819090cc34763ba460ed |
completed | May 3, 2026, 9:02 a.m. |
| PDg | Predicate description generation | batch_69f7117cf2188190b29e36fc1e342c60 |
completed | May 3, 2026, 9:12 a.m. |
Created at: April 28, 2026, 7:35 p.m.