Triple
T37038600
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Dorostol |
E916716
|
entity |
| Predicate | currentMunicipalityCenter |
P147542
|
FINISHED |
| Object | Silistra Municipality |
—
|
NE NERFINISHED |
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: Silistra Municipality | Statement: [Dorostol, currentMunicipalityCenter, Silistra Municipality]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: currentMunicipalityCenter Context triple: [Dorostol, currentMunicipalityCenter, Silistra Municipality]
-
A.
municipalCentre
chosen
Indicates that a location functions as the primary administrative or civic center for a municipality.
-
B.
formerMunicipalityCenterOf
Indicates that an entity once served as the administrative or central seat of a municipality that no longer exists in its former form.
-
C.
isTownCenterOf
Indicates that a location functions as the central, primary area or hub of a specified town.
-
D.
metropolitanRegionCenter
Indicates that one location functions as the central or primary hub of a specified metropolitan region.
-
E.
isSocialCenterOf
Indicates that one entity serves as the primary gathering place or hub for social activities and interactions for another entity or group.
- 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_69f76e93ec4c8190be81cf87354d9155 |
completed | May 3, 2026, 3:49 p.m. |
| NER | Named-entity recognition | batch_69ffa5f31c8881908c26e2aa52df6ece |
completed | May 9, 2026, 9:24 p.m. |
| PD | Predicate disambiguation | batch_69ffa42aee408190ad1a5f285688b338 |
completed | May 9, 2026, 9:16 p.m. |
Created at: May 3, 2026, 4:14 p.m.