Triple
T6364
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Warm Springs, Georgia |
E127
|
entity |
| Predicate | hasGovernmentType |
P220
|
FINISHED |
| Object | mayor–council government |
—
|
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–council government | Statement: [Warm Springs, Georgia, hasGovernmentType, mayor–council government]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasGovernmentType Context triple: [Warm Springs, Georgia, hasGovernmentType, mayor–council government]
-
A.
governmentType
chosen
Indicates the form or system of governance under which an entity (such as a country or organization) is organized and ruled.
-
B.
headOfGovernment
Indicates that one entity serves as the chief executive authority or leader of the government of another entity.
-
C.
governmentBranch
Indicates that one entity functions as an official division or branch within the structure of a government.
-
D.
headOfGovernmentBody
Indicates that one entity serves as the chief executive or leading official in charge of governing another entity, typically a political or administrative body.
-
E.
hasChancellor
Indicates that an entity holds the position or role of chancellor for another entity.
- 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_69a23bb612708190b09f25385e4b63d1 |
completed | Feb. 28, 2026, 12:49 a.m. |
| NER | Named-entity recognition | batch_69a2421836f08190b54fc40edeb1a96b |
completed | Feb. 28, 2026, 1:17 a.m. |
| PD | Predicate disambiguation | batch_69a23fe064c881909496fd0e6b0e18d7 |
completed | Feb. 28, 2026, 1:07 a.m. |
Created at: Feb. 28, 2026, 12:54 a.m.