Triple
T3092833
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Compton, California, United States |
E64522
|
entity |
| Predicate | hasMayorCouncilSystem |
P12191
|
FINISHED |
| Object | yes |
—
|
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: yes | Statement: [Compton, California, United States, hasMayorCouncilSystem, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasMayorCouncilSystem Context triple: [Compton, California, United States, hasMayorCouncilSystem, yes]
-
A.
hasCityCouncil
Indicates that an entity is governed or administered by a specific city council.
-
B.
hasMunicipalGovernment
Indicates that an entity is administered or governed by a municipal-level governmental authority.
-
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.
hasCountyCouncil
Indicates that an entity is administratively governed or overseen by a specific county council.
-
E.
hasMayor
Indicates that one entity serves as the mayor of another entity, typically a city, town, or municipality.
- 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_69ad857c97d88190b26f9b1c90839c77 |
completed | March 8, 2026, 2:19 p.m. |
| NER | Named-entity recognition | batch_69ada21055b88190b602425a513af7e6 |
completed | March 8, 2026, 4:21 p.m. |
| PD | Predicate disambiguation | batch_69ad9ded78f881908be6fc0fb7c35764 |
completed | March 8, 2026, 4:03 p.m. |
Created at: March 8, 2026, 3:03 p.m.