Triple
T26086813
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Serhetabat District |
E658005
|
entity |
| Predicate | formerNameOfCenter |
P65
|
FINISHED |
| Object | Kushka |
—
|
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: Kushka | Statement: [Serhetabat District, formerNameOfCenter, Kushka]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: formerNameOfCenter Context triple: [Serhetabat District, formerNameOfCenter, Kushka]
-
A.
formerName
chosen
Indicates that an entity was previously known by a different name in the past.
-
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.
formerNameOfDistrict
Indicates that one district previously had a different official name, which is the value linked by this predicate.
-
D.
formerlyKnownLocationAs
Indicates that an entity was previously known or referred to by a different location name or designation.
-
E.
formerNameOfAreaWithin
Indicates that one area previously had a different name while remaining within the same larger encompassing area.
- 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_69ee5bbf0d208190801ee95d4f07fb16 |
completed | April 26, 2026, 6:38 p.m. |
| NER | Named-entity recognition | batch_69f74c70fd248190a9d5543afcb08211 |
completed | May 3, 2026, 1:24 p.m. |
| PD | Predicate disambiguation | batch_69f7478e3b548190a51d5d436e2bb036 |
completed | May 3, 2026, 1:03 p.m. |
Created at: April 26, 2026, 7:43 p.m.