Triple
T22036342
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Lubny Uyezd |
E544218
|
entity |
| Predicate | capital |
P234
|
FINISHED |
| Object | Lubny |
—
|
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: Lubny | Statement: [Lubny Uyezd, capital, Lubny]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Lubny Context triple: [Lubny Uyezd, capital, 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.
Zbarazh
Zbarazh is a historic town in western Ukraine known for its medieval castle and role in regional political and military history.
-
C.
Chortkiv
Chortkiv is a historic town in western Ukraine known for its architectural landmarks and role as a local cultural and administrative center.
-
D.
Ruzhyn
Ruzhyn is an urban-type settlement in central Ukraine, historically part of Zhytomyr Oblast and now administered within Bila Tserkva Raion of Kyiv Oblast.
-
E.
Letychiv
Letychiv is an urban-type settlement in western Ukraine known for its historic fortress and role as a local administrative center.
- F. None of above.
- G. Unsure - the case is ambiguous/there is not enough information to decide.
Provenance (2 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_69e11e2f98c8819083e11eab90942a78 |
completed | April 16, 2026, 5:36 p.m. |
| NER | Named-entity recognition | batch_69f127f1f95c8190a324c84313cd91ee |
completed | April 28, 2026, 9:34 p.m. |
Created at: April 16, 2026, 8:25 p.m.