Triple
T23348752
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ivanov |
E591944
|
entity |
| Predicate | hasCharacter |
P2308
|
FINISHED |
| Object | Lvov |
—
|
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: Lvov | Statement: [Ivanov, hasCharacter, Lvov]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Lvov Context triple: [Ivanov, hasCharacter, Lvov]
-
A.
Lvov
chosen
Lvov is a Russian noble family name most notably borne by Georgy Lvov, the first head of the Russian Provisional Government after the February Revolution of 1917.
-
B.
Lemberg
Lemberg is a prominent mountain in the Swabian Jura of Baden-Württemberg, Germany, known as the highest peak in that range.
-
C.
Lemberg
Lemberg is a small commune in northeastern France’s Moselle department, situated in the forested, hilly region known as the Pays de Bitche near the German border.
-
D.
Lwów
Lwów is a historic city in Eastern Europe, now known as Lviv in western Ukraine, long recognized as a major cultural and political center of the region.
-
E.
Lvovna
Lvovna is a Russian patronymic derived from the male given name Lev, traditionally used as the middle name for daughters of men named Lev.
- 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_69e25d20e3d08190bcede87673cafb25 |
completed | April 17, 2026, 4:17 p.m. |
| NER | Named-entity recognition | batch_69f199cb2a3c8190a5c0c8d8735256c7 |
completed | April 29, 2026, 5:40 a.m. |
Created at: April 17, 2026, 5:19 p.m.