Triple
T19616476
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Horki District |
E470872
|
entity |
| Predicate | hasSettlement |
P1068
|
FINISHED |
| Object | Horki |
—
|
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: Horki | Statement: [Horki District, hasSettlement, Horki]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Horki Context triple: [Horki District, hasSettlement, Horki]
-
A.
Horki
chosen
Horki is a town in eastern Belarus known for its agricultural academy and regional administrative significance.
-
B.
Horezu
Horezu is a small Romanian town renowned for its traditional pottery and UNESCO-recognized ceramic craftsmanship.
-
C.
Khirki
Khirki is a historic locality in South Delhi, India, known for its medieval village character and proximity to the ruins of the 14th-century fortified city of Jahanpanah.
-
D.
Uherka
Uherka is a river in eastern Poland that serves as a tributary of the Western Bug, flowing through the Lublin region.
-
E.
Krakhuna
Krakhuna is a Georgian white grape variety from the Imereti region, known for producing aromatic, full-bodied wines with pronounced acidity.
- 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_69d8e510fa248190b7afb274a1d4cf73 |
completed | April 10, 2026, 11:54 a.m. |
| NER | Named-entity recognition | batch_69e640e272808190800c5bccccd64753 |
completed | April 20, 2026, 3:06 p.m. |
Created at: April 10, 2026, 1:43 p.m.