Triple
T29752997
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Poland–Russia border |
E752950
|
entity |
| Predicate | regimeAffectedBy |
P168176
|
FINISHED |
| Object | Schengen Agreement |
—
|
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 Agreement | Statement: [Poland–Russia border, regimeAffectedBy, Schengen Agreement]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: regimeAffectedBy Context triple: [Poland–Russia border, regimeAffectedBy, Schengen Agreement]
-
A.
regimeDefinedBy
Indicates that a particular regime is characterized, specified, or determined by another entity or set of rules.
-
B.
associatedWithRegime
Indicates a relationship where an entity is linked or connected to a particular regime, such as a political, governmental, or ruling system.
-
C.
regimeCharacterizedAs
Indicates that a political or governance regime is described or classified as having a particular character, quality, or type.
-
D.
associatedWithRegimeChange
Indicates a relationship in which an entity is involved in, linked to, or plays a role in bringing about a change in political regime or leadership.
-
E.
regimeName
Indicates that a particular name or label is assigned to a specific regime.
- F. None of above. chosen
Provenance (4 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_69f0d62c84cc8190846f80ae04fdf8ec |
completed | April 28, 2026, 3:45 p.m. |
| NER | Named-entity recognition | batch_69f673c8c00881908596a9e9fca49436 |
completed | May 2, 2026, 9:59 p.m. |
| PD | Predicate disambiguation | batch_69f66ec5bf508190ad088b89455252bd |
completed | May 2, 2026, 9:38 p.m. |
| PDg | Predicate description generation | batch_69f67256d064819094be04fc1bbbc635 |
completed | May 2, 2026, 9:53 p.m. |
Created at: April 28, 2026, 7:54 p.m.