Triple
T1824855
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Domodedovo |
E40627
|
entity |
| Predicate | hasNearbyCity |
P350
|
FINISHED |
| Object | Podolsk |
E115415
|
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: Podolsk | Statement: [Domodedovo, hasNearbyCity, Podolsk]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: Podolsk Context triple: [Domodedovo, hasNearbyCity, Podolsk]
-
A.
Podolsk
chosen
Podolsk is a major industrial city and former center of machine-building located just south of Moscow in western Russia.
-
B.
Priozersk
Priozersk is a small town in northwestern Russia known for its historic fortress Korela and its location on the shores of Lake Ladoga.
-
C.
Smolensk
Smolensk is a historic city in western Russia near the Belarusian border, known for its strategic location and centuries-old fortifications.
-
D.
Elektrostal
Elektrostal is an industrial city in Russia known for its metallurgical and engineering industries, located east of Moscow.
-
E.
Noginsk
Noginsk is a town in western Russia that serves as an industrial and transport center east of Moscow.
- 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_69a8864644bc8190b2358ab897194ac1 |
completed | March 4, 2026, 7:21 p.m. |
| NER | Named-entity recognition | batch_69abb0003d308190a024f8c03c5f5dad |
completed | March 7, 2026, 4:56 a.m. |
| NED1 | Entity disambiguation (via context triple) | batch_69aeb3a777a481909e8b350811ee29c0 |
completed | March 9, 2026, 11:48 a.m. |
Created at: March 4, 2026, 7:32 p.m.