Triple
T22740942
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Montes Municipality |
E562409
|
entity |
| Predicate | governmentSeatType |
P17125
|
FINISHED |
| Object | municipal seat |
—
|
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 seat | Statement: [Montes Municipality, governmentSeatType, municipal seat]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: governmentSeatType Context triple: [Montes Municipality, governmentSeatType, municipal seat]
-
A.
seatOfGovernment
Indicates that a location serves as the administrative center where a government exercises its official authority and conducts its primary governing functions.
-
B.
hasGovernmentSeatType
chosen
Indicates the specific type or classification of the location where a government’s central authority or administrative seat is situated.
-
C.
seatOfGovernmentBranch
Indicates the branch or division of government for which a particular location serves as the seat of authority or administration.
-
D.
hostsSeatOfGovernment
Indicates that a place serves as the location where a government’s central administrative or executive authority is based.
-
E.
placeOfOffice
Indicates the location where an office or official position is held or based.
- 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_69e245513a5c81908d5cb471b4fc429d |
completed | April 17, 2026, 2:36 p.m. |
| NER | Named-entity recognition | batch_69f17972fde8819086094cea289a2af8 |
completed | April 29, 2026, 3:22 a.m. |
| PD | Predicate disambiguation | batch_69eed2a971c0819088af574e40c9343f |
completed | April 27, 2026, 3:06 a.m. |
Created at: April 17, 2026, 3:23 p.m.