Triple
T33441890
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Manan-gu |
E856385
|
entity |
| Predicate | hasMunicipalHierarchyPosition |
P80007
|
FINISHED |
| Object | below city level |
—
|
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: below city level | Statement: [Manan-gu, hasMunicipalHierarchyPosition, below city level]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasMunicipalHierarchyPosition Context triple: [Manan-gu, hasMunicipalHierarchyPosition, below city level]
-
A.
hasMunicipalLevel
chosen
Indicates that an entity is associated with a specific level or tier within a municipal (local government) hierarchy.
-
B.
isPositionHeldInAdministrativeTerritorialEntity
Indicates that a specific position or office is held within a particular administrative or territorial entity (such as a city, region, or country).
-
C.
hasMunicipalSeatFunction
Indicates that an entity serves as the administrative or municipal seat (central governing location) for a municipality.
-
D.
isMunicipalOrgan
Indicates that an entity functions as an official organ or body of a municipal (local) government.
-
E.
hasPositionInOrganization
Indicates that an entity holds a specific role, job, or position within a particular organization.
- 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_69f34971b75881908be360bb041f003c |
completed | April 30, 2026, 12:22 p.m. |
| NER | Named-entity recognition | batch_69fd8ccbd4c88190b13aae0673b3c821 |
completed | May 8, 2026, 7:12 a.m. |
| PD | Predicate disambiguation | batch_69fd8ae2227c819089546f5c3629799e |
completed | May 8, 2026, 7:04 a.m. |
Created at: May 1, 2026, 1:37 a.m.