Triple
T28992014
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | UKDD |
E736049
|
entity |
| Predicate | formerCityNameAssociated |
P40182
|
FINISHED |
| Object | Dnipropetrovsk |
—
|
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: Dnipropetrovsk | Statement: [UKDD, formerCityNameAssociated, Dnipropetrovsk]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: formerCityNameAssociated Context triple: [UKDD, formerCityNameAssociated, Dnipropetrovsk]
-
A.
formerCityName
Indicates that an entity was previously known by a different city name in the past.
-
B.
associatedWithFormerCity
Indicates a relationship where an entity is or was connected to a city that no longer exists in its former status or form (e.g., renamed, dissolved, or merged).
-
C.
formerNameOfRelatedCity
Indicates that one city previously had a different name that was historically used for another, related city.
-
D.
formerCity
Indicates that an entity was once recognized as a city but no longer holds that status.
-
E.
hasAssociatedCityFormerName
chosen
Indicates that an entity is linked to a city by referencing one of that city's former or historical names.
- 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_69f077eacd0481908ef0bafd74491cd0 |
completed | April 28, 2026, 9:03 a.m. |
| NER | Named-entity recognition | batch_69fe38be079c8190a240191ac0e73e3a |
completed | May 8, 2026, 7:25 p.m. |
| PD | Predicate disambiguation | batch_69fe350344508190930de2218156ca02 |
completed | May 8, 2026, 7:09 p.m. |
Created at: April 28, 2026, 9:26 a.m.