Triple
T8787661
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Slovakia and Hungary |
E209079
|
entity |
| Predicate | shareHistoricalConflictContext |
P2746
|
FINISHED |
| Object | interwar border disputes |
—
|
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: interwar border disputes | Statement: [Slovakia and Hungary, shareHistoricalConflictContext, interwar border disputes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: shareHistoricalConflictContext Context triple: [Slovakia and Hungary, shareHistoricalConflictContext, interwar border disputes]
-
A.
conflictHistory
Indicates a history of conflict or antagonistic interactions that have occurred between the related entities.
-
B.
militaryConflict
Indicates a relationship where two or more parties are engaged in organized, armed hostilities or warfare against each other.
-
C.
opponentInHistoricalConflict
Indicates that two entities stood on opposing sides in a specific historical conflict or war.
-
D.
shareHistoricalContextAs
Indicates that two or more entities are associated with or understood within the same historical background, period, or circumstances.
-
E.
historicallyContestedBy
chosen
Indicates that two or more parties have disputed or challenged control, ownership, or interpretation of something over a period of history.
- 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_69ca836168108190bb43d3dc235c1f55 |
completed | March 30, 2026, 2:06 p.m. |
| NER | Named-entity recognition | batch_69cc5f89a84c819085d4cfe4e6dfbda8 |
completed | March 31, 2026, 11:58 p.m. |
| PD | Predicate disambiguation | batch_69cc5c1d48f08190b325a77d4c76d223 |
completed | March 31, 2026, 11:43 p.m. |
Created at: March 30, 2026, 6:43 p.m.