Triple
T38692287
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Coles Creek, Michigan |
E949299
|
entity |
| Predicate | isCharterTownshipLocality |
P191660
|
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: [Coles Creek, Michigan, isCharterTownshipLocality, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isCharterTownshipLocality Context triple: [Coles Creek, Michigan, isCharterTownshipLocality, true]
-
A.
isCivilTownship
Indicates that one entity is a civil township, i.e., an administrative or local government subdivision, in relation to another entity.
-
B.
isCentralLocalityOf
Indicates that a locality serves as the main or central place within a larger administrative or geographic area.
-
C.
isIslandTownship
Indicates that a township is located entirely on an island or consists predominantly of island territory.
-
D.
isProvincialTown
Indicates that a place is classified as a town that serves as an administrative or local center within a province rather than a major city or rural area.
-
E.
hasTownship
Indicates that one administrative area or jurisdiction includes or is associated with a specific township.
- 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_69f76efe16148190befd5dd59c3dfeaa |
completed | May 3, 2026, 3:51 p.m. |
| NER | Named-entity recognition | batch_69fce545fec881909247a3af821d21ae |
completed | May 7, 2026, 7:17 p.m. |
| PD | Predicate disambiguation | batch_69fce12eaeec81908cf81346b2cef6e0 |
completed | May 7, 2026, 6:59 p.m. |
| PDg | Predicate description generation | batch_69fce54532948190a5cfacfe18e09322 |
completed | May 7, 2026, 7:17 p.m. |
Created at: May 3, 2026, 4:33 p.m.