Triple
T8848181
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Клушино |
E210561
|
entity |
| Predicate | расположеноВЕвропе |
P14704
|
FINISHED |
| Object | да |
—
|
LITERAL 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: да | Statement: [Клушино, расположеноВЕвропе, да]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: расположеноВЕвропе Context triple: [Клушино, расположеноВЕвропе, да]
-
A.
europeanRegion
Indicates that an entity is located in, associated with, or classified as part of a region within Europe.
-
B.
locatedInEasternHemisphere
Indicates that the subject is geographically situated within the Eastern Hemisphere of the Earth.
-
C.
isInContinent
chosen
Indicates that one place or region is geographically located within the boundaries of a specific continent.
-
D.
countryLocatedIn
Indicates that a country is geographically or politically situated within a specified larger region, territory, or entity.
-
E.
worldRegion
Indicates that one entity is a geographic region that encompasses, contains, or is associated with the other entity within the world.
- F. None of above.
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_69ca838967bc8190b46c3c80a2887ea4 |
completed | March 30, 2026, 2:07 p.m. |
| NER | Named-entity recognition | batch_69cc60aa6db0819097c3257499200afc |
completed | April 1, 2026, 12:02 a.m. |
| PD | Predicate disambiguation | batch_69cc5c25b874819084c9ba391703e066 |
completed | March 31, 2026, 11:43 p.m. |
Created at: March 30, 2026, 6:49 p.m.