Triple
T710859
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Hungary–Austria border |
E14202
|
entity |
| Predicate | borderRegimeLiberalized |
P13728
|
FINISHED |
| Object | 2 May 1989 |
—
|
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: 2 May 1989 | Statement: [Hungary–Austria border, borderRegimeLiberalized, 2 May 1989]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: borderRegimeLiberalized Context triple: [Hungary–Austria border, borderRegimeLiberalized, 2 May 1989]
-
A.
borderRegime
Indicates the type, rules, or control system governing how movement or interaction is managed across a border between entities.
-
B.
demilitarizedBorderWith
Indicates that a border between two entities exists where military forces, installations, and activities are restricted or prohibited by agreement.
-
C.
hasBorderControlStatus
chosen
Indicates the type or condition of border control that applies to a given entity or location.
-
D.
hasBorderCrossingFunction
Indicates that an entity serves as a location or facility where people, goods, or vehicles can legally cross a border between jurisdictions.
-
E.
customsRegime
Indicates the specific customs treatment or regulatory framework under which goods are imported, exported, or stored.
- 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_69a4934a36e081909e7abef98b898a4e |
completed | March 1, 2026, 7:28 p.m. |
| NER | Named-entity recognition | batch_69a4a77fcc6881908a025bb21e44ad56 |
completed | March 1, 2026, 8:54 p.m. |
| PD | Predicate disambiguation | batch_69a4a4f221b081909fbaa689fb20eb3e |
completed | March 1, 2026, 8:43 p.m. |
Created at: March 1, 2026, 7:36 p.m.