Triple
T13697855
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Switzerland and Liechtenstein |
E328433
|
entity |
| Predicate | shareSchengenArea |
P110139
|
FINISHED |
| Object | yes |
—
|
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: yes | Statement: [Switzerland and Liechtenstein, shareSchengenArea, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: shareSchengenArea Context triple: [Switzerland and Liechtenstein, shareSchengenArea, yes]
-
A.
hasSchengenArea
Indicates that a place, country, or region is part of, or included within, the Schengen Area for border-free movement.
-
B.
isSchengenExternalBorder
Indicates that a given border segment functions as an external boundary between the Schengen Area and non-Schengen territories.
-
C.
supportsSchengenFlights
Indicates that an entity enables or accommodates flights operating within the Schengen Area.
-
D.
haveSimilarStatusInSchengen
chosen
Indicates that two entities share a comparable legal or administrative status within the Schengen area.
-
E.
shareVisaPolicy
Indicates that two entities apply the same or highly similar visa requirements and entry rules to travelers.
- 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_69d8076ff62081908a7bd79889edd7a0 |
completed | April 9, 2026, 8:09 p.m. |
| NER | Named-entity recognition | batch_69dbc878b57c819094e7ea6d1a64211f |
completed | April 12, 2026, 4:29 p.m. |
| PD | Predicate disambiguation | batch_69dbbe9059488190a8113177c83e1481 |
completed | April 12, 2026, 3:47 p.m. |
Created at: April 9, 2026, 9:54 p.m.