Triple
T31951670
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Lower Austria and South Moravia |
E815795
|
entity |
| Predicate | partOfEUInternalBorder |
P106527
|
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: [Lower Austria and South Moravia, partOfEUInternalBorder, Schengen Area]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: partOfEUInternalBorder Context triple: [Lower Austria and South Moravia, partOfEUInternalBorder, Schengen Area]
-
A.
EUInternalBorder
chosen
Indicates that a border lies between two member states within the European Union, where internal EU border rules apply.
-
B.
isSchengenExternalBorder
Indicates that a given border segment functions as an external boundary between the Schengen Area and non-Schengen territories.
-
C.
wasInnerGermanBorder
Indicates that a location or boundary segment functioned as part of the former inner German border separating East and West Germany.
-
D.
borderTypeWithAustria
Indicates the type or nature of the border that an entity shares with Austria.
-
E.
borderTypeWithGermany
Indicates the type or nature of the border that an entity shares with Germany.
- 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_69f348f42d188190a33fc8d20ec50517 |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_69ff7ae5d088819089aa3b6360b6b749 |
completed | May 9, 2026, 6:20 p.m. |
| PD | Predicate disambiguation | batch_69ff7a4df6488190bf60d675b36b1d6d |
completed | May 9, 2026, 6:17 p.m. |
Created at: May 1, 2026, 12:07 a.m.