Triple
T34962676
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Могилёв-Подольский |
E1008301
|
entity |
| Predicate | имеетПограничныйПереходС |
P4105
|
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.
hasBorderCrossing
chosen
Indicates that there exists a point or facility where movement or transit is possible between the boundaries of two adjacent regions or jurisdictions.
-
B.
hasBorderPostWith
Indicates that two regions or territories share a border where an official border post or checkpoint is located between them.
-
C.
hasBorderCrossingFunction
Indicates that an entity serves as a location or facility where people, goods, or vehicles can legally cross a border between jurisdictions.
-
D.
hasBorderCrossingSide
Indicates that one side of a border crossing is associated with or located on a particular boundary or segment of that crossing.
-
E.
hasRailBorderCrossing
Indicates that two places are connected by at least one official border crossing that is served by rail transport.
- 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_69f791cc969c8190bf187d6031a030d5 |
completed | May 3, 2026, 6:19 p.m. |
| PD | Predicate disambiguation | batch_69f791033d288190b118029fe412b9c9 |
completed | May 3, 2026, 6:16 p.m. |
Created at: May 3, 2026, 4 p.m.