Triple
T2390865
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Mohrungen |
E48937
|
entity |
| Predicate | hasMunicipalRights |
P37705
|
FINISHED |
| Object | town |
—
|
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: town | Statement: [Mohrungen, hasMunicipalRights, town]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasMunicipalRights Context triple: [Mohrungen, hasMunicipalRights, town]
-
A.
hasMunicipalGovernment
Indicates that an entity is administered or governed by a municipal-level governmental authority.
-
B.
isMunicipalStatus
chosen
Indicates that an entity possesses a specific legally defined municipal status or classification within a governmental or administrative system.
-
C.
hasMunicipalFormation
Indicates that an administrative or territorial unit is organized into, or associated with, a specific municipal formation as its local self-governing structure.
-
D.
hasMunicipalService
Indicates that a municipality provides or is responsible for a specific public service to a given area, facility, or population.
-
E.
hasVoivodeshipRights
Indicates that an entity possesses the legal status, privileges, or jurisdictional authority associated with a voivodeship (a regional administrative unit).
- 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_69a88aa5f63081908d07fd302029fcbd |
completed | March 4, 2026, 7:40 p.m. |
| NER | Named-entity recognition | batch_69abc87457388190822d5506327db8f2 |
completed | March 7, 2026, 6:40 a.m. |
| PD | Predicate disambiguation | batch_69abc5a1b5748190b4cd8989700f4dd2 |
completed | March 7, 2026, 6:28 a.m. |
Created at: March 4, 2026, 7:57 p.m.