Triple
T12181608
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Lida Castle |
E290232
|
entity |
| Predicate | locatedIn |
P40
|
FINISHED |
| Object | Lida |
E290232
|
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: Lida | Statement: [Lida Castle, locatedIn, Lida]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Lida Context triple: [Lida Castle, locatedIn, Lida]
-
A.
Lida
chosen
Lida is a historic city in present-day western Belarus, known for its medieval castle and former role as a regional center in the Grand Duchy of Lithuania.
-
B.
Lidan
Lidan is a river in southwestern Sweden that flows through the historical province of Västergötland before emptying into Lake Vänern.
-
C.
Luga
Luga is a small historic town in northwestern Russia known for its strategic location and role in regional transport and industry.
-
D.
Livny
Livny is a historic town in western Russia known as one of the principal urban centers of Oryol Oblast.
-
E.
Tarusa
Tarusa is a small historic town in western Russia known for its scenic location on the Oka River and its associations with Russian artists and writers.
- 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_69d6ab64de5881908d56eb7a75c6cc69 |
completed | April 8, 2026, 7:24 p.m. |
| NER | Named-entity recognition | batch_69d915fd8dac8190928059ad2b6bbbf3 |
completed | April 10, 2026, 3:23 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69f5f6acee6481908ee4129956c98c52 |
completed | May 2, 2026, 1:05 p.m. |
Created at: April 8, 2026, 9:50 p.m.