Triple
T34235217
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Trans-Ili Alatau region |
E878316
|
entity |
| Predicate | hasFormerNearbyCityName |
P179772
|
FINISHED |
| Object | Verny |
—
|
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: Verny | Statement: [Trans-Ili Alatau region, hasFormerNearbyCityName, Verny]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasFormerNearbyCityName Context triple: [Trans-Ili Alatau region, hasFormerNearbyCityName, Verny]
-
A.
hasAssociatedCityFormerName
Indicates that an entity is linked to a city by referencing one of that city's former or historical names.
-
B.
hasNearbyCityRenamedIn
Indicates that a nearby city underwent a renaming event during a specified time or within a particular temporal context.
-
C.
hasOldCity
Indicates that an entity possesses or contains an old or historic city as part of its domain or structure.
-
D.
formerCityNameNearby
chosen
Indicates that an entity is located near a place that used to have a particular city name in the past.
-
E.
cityPreviouslyLocatedIn
Indicates that a city was formerly situated within a specified location or administrative region, but is no longer located there.
- 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_69f349b22d8c819096b22df268382aa9 |
completed | April 30, 2026, 12:23 p.m. |
| NER | Named-entity recognition | batch_69fddac4e2f48190a9301d3422658b29 |
completed | May 8, 2026, 12:44 p.m. |
| PD | Predicate disambiguation | batch_69fdda06969c8190b5d033964ea2a690 |
completed | May 8, 2026, 12:41 p.m. |
Created at: May 1, 2026, 1:56 a.m.