Triple
T34864447
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Zosin–Ustyluh |
E1004972
|
entity |
| Predicate | isOnExternalBorderOf |
P37800
|
FINISHED |
| Object | Schengen Area |
—
|
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: Schengen Area | Statement: [Zosin–Ustyluh, isOnExternalBorderOf, Schengen Area]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isOnExternalBorderOf Context triple: [Zosin–Ustyluh, isOnExternalBorderOf, Schengen Area]
-
A.
liesOnBorderOf
Indicates that one entity is located along or directly adjacent to the boundary line separating it from another entity.
-
B.
isBoundaryFor
Indicates that one entity serves as the limiting edge, border, or enclosing extent that defines the spatial or conceptual bounds of another entity.
-
C.
borderIsInternalTo
Indicates that the boundary or border of one entity lies entirely within the interior of another entity, without crossing or extending outside it.
-
D.
operatesOnBorderWith
Indicates that one entity conducts activities or exerts influence along or across the shared border it has with another entity.
-
E.
hasBorderRelation
chosen
Indicates that one entity shares a boundary or border with 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_69f76dbb678081909a247b9b5e1a73ac |
completed | May 3, 2026, 3:46 p.m. |
| NER | Named-entity recognition | batch_69f782f4f10081908f97f6d0d2dbeec7 |
completed | May 3, 2026, 5:16 p.m. |
| PD | Predicate disambiguation | batch_69f780ff71cc8190a67e71076fbad81a |
completed | May 3, 2026, 5:08 p.m. |
Created at: May 3, 2026, 4 p.m.