Triple
T5747335
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Poltava Governorate |
E126766
|
entity |
| Predicate | contains |
P35
|
FINISHED |
| Object | Lubny |
E443583
|
NE FINISHED |
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: Lubny | Statement: [Poltava Governorate, contains, Lubny]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Lubny Context triple: [Poltava Governorate, contains, Lubny]
-
A.
Lubny
chosen
Lubny is a historic city in central Ukraine known for its role in regional trade and culture since medieval times.
-
B.
Berezhany
Berezhany is a historic town in western Ukraine’s Ternopil Oblast, known for its well-preserved Renaissance castle and multicultural heritage.
-
C.
Kremenets
Kremenets is a historic town in western Ukraine known for its rich cultural heritage and once-significant Jewish community.
-
D.
Vyshhorod
Vyshhorod is a historic town near Kyiv in northern Ukraine, known as a medieval residence of Kyivan Rus' princes and now an industrial and cultural center on the Dnieper River.
-
E.
Pryluky
Pryluky is a historic city in northern Ukraine known for its Cossack heritage and role as a regional cultural and economic center.
- F. None of above.
- G. Unsure - the case is ambiguous/there is not enough information to decide.
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_69c0083179548190b384b0bf3c08ca4d |
completed | March 22, 2026, 3:18 p.m. |
| NER | Named-entity recognition | batch_69c02885b0288190835809681a364b1f |
completed | March 22, 2026, 5:36 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69c07e30fe98819096ad6e09fbd463b5 |
completed | March 22, 2026, 11:41 p.m. |
Created at: March 22, 2026, 3:48 p.m.