Triple
T34864431
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Zosin–Ustyluh |
E1004972
|
entity |
| Predicate | controlsBorderOf |
P144415
|
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, controlsBorderOf, Schengen Area]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: controlsBorderOf Context triple: [Zosin–Ustyluh, controlsBorderOf, Schengen Area]
-
A.
hasOwnBorderControls
Indicates that an entity independently manages and enforces its own border control policies and procedures, separate from those of other entities.
-
B.
formsBorderWithin
Indicates that one entity constitutes a boundary or border located entirely within the spatial extent of another entity.
-
C.
guardedBorderWith
chosen
Indicates a relationship where a shared border between two entities is actively protected or monitored, typically for security or control purposes.
-
D.
borderColor
Indicates the color that forms the boundary or outline of an entity.
-
E.
borderArea
Indicates that an area lies along or near the boundary between two regions, countries, or territories.
- 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_69fec00f27988190955de6b6348a4d97 |
completed | May 9, 2026, 5:03 a.m. |
| PD | Predicate disambiguation | batch_69febd52037c8190b475dbd50fdbc13e |
completed | May 9, 2026, 4:51 a.m. |
Created at: May 3, 2026, 4 p.m.