Triple
T11596528
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Lenin Square (Mahilyow) |
E275015
|
entity |
| Predicate | locatedIn |
P40
|
FINISHED |
| Object | Mahilyow |
E56180
|
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: Mahilyow | Statement: [Lenin Square (Mahilyow), locatedIn, Mahilyow]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Mahilyow Context triple: [Lenin Square (Mahilyow), locatedIn, Mahilyow]
-
A.
Mahilyow
chosen
Mahilyow is a major city in eastern Belarus, serving as an important cultural, economic, and administrative center of the region.
-
B.
Mahilyowskaya
Mahilyowskaya is a metro station on the Minsk Metro system in Minsk, Belarus.
-
C.
Mikolow
Mikolow is a town in southern Poland’s Silesian Voivodeship, known for its historic center and proximity to the regional capital Katowice.
-
D.
Minsk
Minsk is the capital and largest city of Belarus, serving as its political, economic, and cultural center.
-
E.
Beltsy
Beltsy is an alternative name for Bălți, a major city in northern Moldova known as an important economic and cultural 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_69d6aae6b14c81908dc5a74bad7591f9 |
completed | April 8, 2026, 7:22 p.m. |
| NER | Named-entity recognition | batch_69d89549c870819086e16e9110bbad87 |
completed | April 10, 2026, 6:14 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69ee86f246848190a5b020c3e05d02dd |
completed | April 26, 2026, 9:43 p.m. |
Created at: April 8, 2026, 9:38 p.m.