Triple
T34962662
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Могилёв-Подольский |
E1008301
|
entity |
| Predicate | расположенУГраницыС |
P67212
|
FINISHED |
| Object | Молдова |
—
|
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: Молдова | Statement: [Могилёв-Подольский, расположенУГраницыС, Молдова]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: расположенУГраницыС Context triple: [Могилёв-Подольский, расположенУГраницыС, Молдова]
-
A.
разположенНаГраницаМежду
Indicates that something is located on or along the boundary between two entities.
-
B.
протекаетВдольГраницыС
Indicates that one entity (such as a geographic feature or object) runs or extends along the boundary shared with another entity.
-
C.
borderedBy
Indicates that one entity shares a common boundary or edge with another entity.
-
D.
bordersDefinedIn
Indicates that the boundaries or borders of one entity are specified, established, or formally described within another entity (such as a document, dataset, or legal instrument).
-
E.
liesOnBorderOf
chosen
Indicates that one entity is located along or directly adjacent to the boundary line separating it from another entity.
- 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_69f76dc69564819099e9e78aed6ff0a6 |
completed | May 3, 2026, 3:46 p.m. |
| NER | Named-entity recognition | batch_69f78ce78b508190955848e133398dc8 |
completed | May 3, 2026, 5:59 p.m. |
| PD | Predicate disambiguation | batch_69f78b8f4cc08190b49fccd798cb25d7 |
completed | May 3, 2026, 5:53 p.m. |
Created at: May 3, 2026, 4 p.m.