Triple
T34079554
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Akmolinsk Oblast (historical) |
E873995
|
entity |
| Predicate | centralCityNowKnownAs |
P22915
|
FINISHED |
| Object | Astana |
—
|
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: Astana | Statement: [Akmolinsk Oblast (historical), centralCityNowKnownAs, Astana]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: centralCityNowKnownAs Context triple: [Akmolinsk Oblast (historical), centralCityNowKnownAs, Astana]
-
A.
cityNowKnownAs
chosen
Indicates that a city has changed its name and specifies the new name it is currently known by.
-
B.
cityThenKnownAs
Indicates that an entity had a particular city name during a specified earlier time period, before it was renamed or became known by a different name.
-
C.
capitalLaterKnownAs
Indicates that an entity served as a capital city under one name at a given time and was later known by a different name.
-
D.
formerCityName
Indicates that an entity was previously known by a different city name in the past.
-
E.
formerNameOfCapital
Indicates that one entity was the previous official name of a capital city before it was renamed.
- 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_69f349a566808190a1c63b898f33cddf |
completed | April 30, 2026, 12:23 p.m. |
| NER | Named-entity recognition | batch_69fd67191cf88190b53ecbf5be3564e9 |
completed | May 8, 2026, 4:31 a.m. |
| PD | Predicate disambiguation | batch_69fd654fdaac81908e67e75194710f06 |
completed | May 8, 2026, 4:23 a.m. |
Created at: May 1, 2026, 1:52 a.m.