Triple
T3658525
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Slovenia–Italy border |
E77592
|
entity |
| Predicate | changedStatus |
P35872
|
FINISHED |
| Object | became internal Schengen border in 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: became internal Schengen border in 2007 | Statement: [Slovenia–Italy border, changedStatus, became internal Schengen border in 2007]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: changedStatus Context triple: [Slovenia–Italy border, changedStatus, became internal Schengen border in 2007]
-
A.
statusChange
chosen
Indicates a transition in an entity’s state or condition from one status to another over time.
-
B.
laterStatus
Indicates that one entity represents a subsequent or resulting status or condition of another entity in time.
-
C.
changeReason
Indicates the reason or justification for a modification or change made to an entity or its state.
-
D.
statusChangeRule
Indicates a rule or condition that governs how and when an entity’s status is allowed to change from one state to another.
-
E.
changedNameIn
Indicates that an entity has altered or adopted a different name within a specific context, time period, or jurisdiction.
- 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_69ad85dfc4dc8190a441864202ab2a7a |
completed | March 8, 2026, 2:21 p.m. |
| NER | Named-entity recognition | batch_69adc3d48a2081908ac0f76d548a53ee |
completed | March 8, 2026, 6:45 p.m. |
| PD | Predicate disambiguation | batch_69adb847e9d881909dad2ffd0f3b6c15 |
completed | March 8, 2026, 5:56 p.m. |
Created at: March 8, 2026, 3:25 p.m.