Triple
T20894618
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Alexander Mogilny |
E514499
|
entity |
| Predicate | familyName |
P18
|
FINISHED |
| Object | Mogilny |
—
|
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: Mogilny | Statement: [Alexander Mogilny, familyName, Mogilny]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Mogilny Context triple: [Alexander Mogilny, familyName, Mogilny]
-
A.
Mogilny
chosen
Mogilny is the surname of Alexander Mogilny, a prominent Russian-born former professional ice hockey player and NHL star.
-
B.
Mogilno
Mogilno is a historic town in north-central Poland known for its medieval monastery and location in the Kuyavian-Pomeranian Voivodeship.
-
C.
Mogielica
Mogielica is a prominent mountain peak in southern Poland, known for its scenic hiking trails and panoramic views of the Beskid Wyspowy range.
-
D.
Mazyr
Mazyr is an industrial city in southern Belarus known for its oil refinery and location on the Pripyat River.
-
E.
Melnikovo
Melnikovo is a rural settlement located within the Priozersky District of Leningrad Oblast in northwestern Russia.
- 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_69e0b4f7ebe48190952a85547a0f31a1 |
completed | April 16, 2026, 10:07 a.m. |
| NER | Named-entity recognition | batch_69e6d06129788190b88ab807af4641c1 |
completed | April 21, 2026, 1:18 a.m. |
Created at: April 16, 2026, 12:47 p.m.