Triple
T12468524
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Erin Township, Minnesota |
E297990
|
entity |
| Predicate | isCivilTownship |
P105162
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [Erin Township, Minnesota, isCivilTownship, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isCivilTownship Context triple: [Erin Township, Minnesota, isCivilTownship, true]
-
A.
hasTownship
Indicates that one administrative area or jurisdiction includes or is associated with a specific township.
-
B.
isInteriorTownOf
Indicates that one town is located within the interior region of, and is administratively or geographically associated with, a larger area or jurisdiction.
-
C.
isSuburbanMunicipality
Indicates that a municipality is located in a suburban area, typically surrounding or adjacent to a larger urban center.
-
D.
isMunicipal
Indicates that something belongs to, is administered by, or is characteristic of a municipality or local city government.
-
E.
isMunicipalCorporationOf
Indicates that an entity functions as the municipal governing body responsible for administering and managing the affairs of a specified city or urban area.
- 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_69d6ada270808190b1a2b2e7b02bb426 |
completed | April 8, 2026, 7:33 p.m. |
| NER | Named-entity recognition | batch_69d94e626dbc8190ac7dcdb542ba9b0c |
completed | April 10, 2026, 7:24 p.m. |
| PD | Predicate disambiguation | batch_69d94d3f701c81909dd0e00251ac8553 |
completed | April 10, 2026, 7:19 p.m. |
| PDg | Predicate description generation | batch_69d94e5f8d04819086d1ad4d62364005 |
completed | April 10, 2026, 7:24 p.m. |
Created at: April 8, 2026, 9:56 p.m.