Triple
T35240160
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | García |
E1017489
|
entity |
| Predicate | electoralDistrictLevel |
P119959
|
FINISHED |
| Object | municipal |
—
|
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: municipal | Statement: [García, electoralDistrictLevel, municipal]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: electoralDistrictLevel Context triple: [García, electoralDistrictLevel, municipal]
-
A.
electorateLevel
Indicates the degree or tier of political constituency or voting body at which a decision, representation, or electoral process is defined or applied.
-
B.
electoralDistrictType
Indicates the specific category or kind of electoral district associated with an entity (e.g., federal, state, local).
-
C.
hasElectoralLevel
chosen
Indicates that one entity is associated with a specific tier or level within an electoral or voting system.
-
D.
administrativeDistrictLevel
Indicates the hierarchical level or tier of an administrative district within a broader governmental or territorial structure.
-
E.
electoralDistrictStructure
Indicates how electoral districts are organized, defined, or structured in relation to one another within an electoral system.
- 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_69f76de235048190b990070c23c51b6b |
completed | May 3, 2026, 3:46 p.m. |
| NER | Named-entity recognition | batch_69ff409ff5548190849c2d50e99bd807 |
completed | May 9, 2026, 2:11 p.m. |
| PD | Predicate disambiguation | batch_69ff401a5e188190a72f945e910b4a6c |
completed | May 9, 2026, 2:09 p.m. |
Created at: May 3, 2026, 4:02 p.m.