Triple
T22464288
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Sleman City Hall |
E555309
|
entity |
| Predicate | typeOfGovernmentBodyServed |
P70158
|
FINISHED |
| Object | regency 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: regency government | Statement: [Sleman City Hall, typeOfGovernmentBodyServed, regency government]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: typeOfGovernmentBodyServed Context triple: [Sleman City Hall, typeOfGovernmentBodyServed, regency government]
-
A.
governmentTypeServed
chosen
Indicates the type of government that an entity serves, is affiliated with, or operates under in its role or function.
-
B.
governmentBodyServed
Indicates that one entity has served in an official capacity within, or as a member of, a particular government body.
-
C.
governmentServed
Indicates that a person has held a position serving in or working for a particular government.
-
D.
legislatureTypeServed
Indicates the type of legislative body in which an entity has served (e.g., national, state, or local legislature).
-
E.
governingBodyOfType
Indicates that an entity serves as the official governing body for another entity of a specified type or category.
- 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_69e11e51fdec8190adfdf9f8a6362221 |
completed | April 16, 2026, 5:37 p.m. |
| NER | Named-entity recognition | batch_69f15b82549c8190943c0940bb90bafc |
completed | April 29, 2026, 1:14 a.m. |
| PD | Predicate disambiguation | batch_69e898b6eee08190ba673a0ee329e671 |
completed | April 22, 2026, 9:45 a.m. |
Created at: April 16, 2026, 8:48 p.m.