Triple
T29253166
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Barton Township, Michigan |
E741623
|
entity |
| Predicate | isAdminTerritoryWithin |
P8351
|
FINISHED |
| Object | Mecosta County, Michigan |
—
|
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: Mecosta County, Michigan | Statement: [Barton Township, Michigan, isAdminTerritoryWithin, Mecosta County, Michigan]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isAdminTerritoryWithin Context triple: [Barton Township, Michigan, isAdminTerritoryWithin, Mecosta County, Michigan]
-
A.
isForTerritory
Indicates that something is intended to define, cover, or apply to a specific territory or geographic area.
-
B.
adminTerritory
Indicates that one entity serves as the administrative authority or governing jurisdiction over a specified territory.
-
C.
adminTerritoryName
Indicates the name assigned to an administrative territory within a larger governance or organizational structure.
-
D.
hasComponentTerritory
chosen
Indicates that one territory is a constituent or subordinate part of a larger, encompassing territory.
-
E.
usesTerritoryFor
Indicates that an entity employs or exploits a particular territory for a specific purpose, function, or activity.
- 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_69f0911eba2c8190b07cd2fdf91422c9 |
completed | April 28, 2026, 10:51 a.m. |
| NER | Named-entity recognition | batch_69f664aaeec88190afa894d26edbcf8b |
completed | May 2, 2026, 8:55 p.m. |
| PD | Predicate disambiguation | batch_69f660f2e3708190ab658652bcfc04d0 |
completed | May 2, 2026, 8:39 p.m. |
Created at: April 28, 2026, 12:35 p.m.