Triple
T2983962
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Milton, Georgia |
E80576
|
entity |
| Predicate | mayorCouncilType |
P12191
|
FINISHED |
| Object | mayor and city council |
—
|
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: mayor and city council | Statement: [Milton, Georgia, mayorCouncilType, mayor and city council]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: mayorCouncilType Context triple: [Milton, Georgia, mayorCouncilType, mayor and city council]
-
A.
mayorType
Indicates the specific category or role classification of a mayor in relation to their office or jurisdiction.
-
B.
councilType
Indicates the specific kind or classification of a council that an entity is associated with or designated as.
-
C.
mayorCouncilForm
chosen
Indicates that a municipality operates under a mayor–council form of government, where executive authority is vested in an elected mayor and legislative authority in an elected council.
-
D.
hasCityCouncil
Indicates that an entity is governed or administered by a specific city council.
-
E.
council
Indicates that an entity serves as a governing or advisory council for another entity or within a particular domain.
- 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_69ad8b15f6ac8190be5fd16a33edcb4f |
completed | March 8, 2026, 2:43 p.m. |
| NER | Named-entity recognition | batch_69ad99c481fc81909971c96352a881b4 |
completed | March 8, 2026, 3:46 p.m. |
| PD | Predicate disambiguation | batch_69ad9611fc348190a5d17d237f653f60 |
completed | March 8, 2026, 3:30 p.m. |
Created at: March 8, 2026, 2:59 p.m.