Triple
T26007429
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Nuijamaa |
E646796
|
entity |
| Predicate | SchengenExternalBorder |
P109217
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [Nuijamaa, SchengenExternalBorder, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: SchengenExternalBorder Context triple: [Nuijamaa, SchengenExternalBorder, true]
-
A.
isSchengenExternalBorder
chosen
Indicates that a given border segment functions as an external boundary between the Schengen Area and non-Schengen territories.
-
B.
EUInternalBorder
Indicates that a border lies between two member states within the European Union, where internal EU border rules apply.
-
C.
borderStation
Indicates a facility or checkpoint located at or near a border where cross-boundary movement, control, or processing of people or goods occurs.
-
D.
borderControlSide
Indicates that one entity is positioned on or associated with a particular side or segment of a border control area or checkpoint.
-
E.
hasBorderControlBy
Indicates that the border of one entity is monitored, regulated, or managed by 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_69e77e89d5848190b54352cdb74f6029 |
completed | April 21, 2026, 1:41 p.m. |
| NER | Named-entity recognition | batch_69f6057bd2708190bf400b153aca2f1b |
completed | May 2, 2026, 2:09 p.m. |
| PD | Predicate disambiguation | batch_69f4a10728e08190bc0b96c558740f51 |
completed | May 1, 2026, 12:48 p.m. |
Created at: April 22, 2026, 9:01 a.m.