Triple
T13578810
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Greece and Bulgaria |
E324355
|
entity |
| Predicate | shareEUExternalBorderUntil2007 |
P16110
|
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: [Greece and Bulgaria, shareEUExternalBorderUntil2007, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: shareEUExternalBorderUntil2007 Context triple: [Greece and Bulgaria, shareEUExternalBorderUntil2007, yes]
-
A.
EUInternalBorder
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.
SchengenEntryDate
Indicates the date on which an entity entered the Schengen Area.
-
D.
EUOutermostRegionSince
Indicates that an entity has held the status of an EU outermost region continuously since a specified point in time.
-
E.
borderHistory
chosen
Indicates the historical changes, events, or status of borders between entities over time.
- 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_69d80769100c819099111274614f5ed2 |
completed | April 9, 2026, 8:09 p.m. |
| NER | Named-entity recognition | batch_69dbb03052088190a2b68c106059828e |
completed | April 12, 2026, 2:46 p.m. |
| PD | Predicate disambiguation | batch_69dbae161a0481909f9d3f40ca4e0ac5 |
completed | April 12, 2026, 2:37 p.m. |
Created at: April 9, 2026, 9:48 p.m.