Triple
T36949848
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Decatur, Michigan |
E914027
|
entity |
| Predicate | hasVillagePresident |
P123058
|
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: [Decatur, Michigan, hasVillagePresident, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasVillagePresident Context triple: [Decatur, Michigan, hasVillagePresident, true]
-
A.
hasCivicLeader
Indicates that an entity serves as the civic leader (such as a mayor or equivalent public official) of another entity, typically a city or municipality.
-
B.
hasVillageAtHead
Indicates that a village is located at the head (source or upper end) of a geographic feature such as a valley, river, or bay.
-
C.
hasTribalChairperson
Indicates that an entity is associated with a specific tribal chairperson who serves as its leader or official representative.
-
D.
hasViceMayor
Indicates that an entity holds the position of vice mayor for a given administrative or governmental body.
-
E.
hasHeadOfLocalGovernment
chosen
Indicates that an administrative area is associated with the person who serves as its chief local government official.
- 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_69f76e8b28848190abd81fe7a7374910 |
completed | May 3, 2026, 3:49 p.m. |
| NER | Named-entity recognition | batch_69fd884cb2b48190b6acd473430d9e19 |
completed | May 8, 2026, 6:53 a.m. |
| PD | Predicate disambiguation | batch_69fd8709ca208190a8bab836f0156af5 |
completed | May 8, 2026, 6:47 a.m. |
Created at: May 3, 2026, 4:13 p.m.