Triple
T28571090
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Mayor of Tamba |
E723115
|
entity |
| Predicate | hasLegalJurisdictionLevel |
P6712
|
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: [Mayor of Tamba, hasLegalJurisdictionLevel, municipal]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasLegalJurisdictionLevel Context triple: [Mayor of Tamba, hasLegalJurisdictionLevel, municipal]
-
A.
jurisdictionLevel
chosen
Indicates the scope or tier of authority under which an entity or action is legally governed or regulated.
-
B.
hasJurisidiction
Indicates that one entity holds legal authority or control over another entity, area, or matter.
-
C.
hasJurisdictionStatus
Indicates that an authority or entity holds a particular legal or administrative jurisdictional status over a specified domain, area, or matter.
-
D.
hasJurisdictionOver
Indicates that one authority or governing body holds legal power or control to make and enforce decisions over another entity, area, or matter.
-
E.
usesJurisdiction
Indicates that one entity applies or operates under the legal authority or rules of a particular jurisdiction.
- 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_69f01d7e97708190ae9e77ee66a68abd |
completed | April 28, 2026, 2:37 a.m. |
| NER | Named-entity recognition | batch_69f739a638748190808e7a2930dce16e |
completed | May 3, 2026, 12:03 p.m. |
| PD | Predicate disambiguation | batch_69f732f2dc6c8190a4e86da98cc5eb05 |
completed | May 3, 2026, 11:35 a.m. |
Created at: April 28, 2026, 4:09 a.m.