Triple
T38334430
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Czechoslovakia–Hungary border |
E1037912
|
entity |
| Predicate | historicalSuccessorBorder |
—
|
GENERATED |
| Object | Slovakia–Hungary border |
—
|
UNRECOGNIZED GENERATED |
How this triple was built (1 step)
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.
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: historicalSuccessorBorder Context triple: [Czechoslovakia–Hungary border, historicalSuccessorBorder, Slovakia–Hungary border]
-
A.
successorBorder
chosen
Indicates that one entity’s border directly follows or replaces another entity’s border in a sequence or progression.
-
B.
historicalSuccessorState
Indicates that one state historically followed and replaced another state in time as its successor.
-
C.
historicalSuccessorInNationStateContext
Indicates that one political entity directly follows another as its successor within the historical continuity of a nation-state.
-
D.
predecessorBorderWith
Indicates that one entity previously shared a common border with another entity in an earlier time or version.
-
E.
historicalRegionSuccessor
Indicates that one historical region directly follows and replaces another in terms of territorial or administrative continuity.
- F. None of above.
Provenance (1 batch)
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_69f76e20d65c81909619ac0dd85c56f0 |
completed | May 3, 2026, 3:47 p.m. |
Created at: May 3, 2026, 4:30 p.m.