Triple
T6651795
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Polish–German border |
E150838
|
entity |
| Predicate | isSchengenBorderSince |
P21386
|
FINISHED |
| Object | 2007 |
—
|
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: 2007 | Statement: [Polish–German border, isSchengenBorderSince, 2007]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isSchengenBorderSince Context triple: [Polish–German border, isSchengenBorderSince, 2007]
-
A.
hasSchengenArea
Indicates that a place, country, or region is part of, or included within, the Schengen Area for border-free movement.
-
B.
SchengenEntryDate
chosen
Indicates the date on which an entity entered the Schengen Area.
-
C.
hasBorderPostWith
Indicates that two regions or territories share a border where an official border post or checkpoint is located between them.
-
D.
hasBorderControlStatus
Indicates the type or condition of border control that applies to a given entity or location.
-
E.
hasBorderMeetingCountry
Indicates that one country shares a land or maritime border with another country.
- 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_69c687f2c9508190a60b9aad31d3f358 |
completed | March 27, 2026, 1:36 p.m. |
| NER | Named-entity recognition | batch_69c6cc9c6cb0819084fec8e0beb430de |
completed | March 27, 2026, 6:29 p.m. |
| PD | Predicate disambiguation | batch_69c6ad04d66c8190926ffcbff372643b |
completed | March 27, 2026, 4:15 p.m. |
Created at: March 27, 2026, 2:01 p.m.