Triple
T7147139
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Poland–Czech Republic border |
E166595
|
entity |
| Predicate | cameIntoExistenceAfter |
P3117
|
FINISHED |
| Object | dissolution of Czechoslovakia |
—
|
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: dissolution of Czechoslovakia | Statement: [Poland–Czech Republic border, cameIntoExistenceAfter, dissolution of Czechoslovakia]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: cameIntoExistenceAfter Context triple: [Poland–Czech Republic border, cameIntoExistenceAfter, dissolution of Czechoslovakia]
-
A.
existedAfter
Indicates that one entity came into existence only after another entity already existed.
-
B.
tookPlaceAfter
Indicates that one event or occurrence happened later in time than another event or occurrence.
-
C.
existsSince
Indicates that an entity has been in existence or valid from a specified point in time onward.
-
D.
createdAfterEvent
chosen
Indicates that the creation of one entity occurred after a specified event in time.
-
E.
bornAfter
Indicates that one entity’s birth occurred later in time than another entity’s birth.
- 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_69c68886779c8190a8e3fbabffe68253 |
completed | March 27, 2026, 1:39 p.m. |
| NER | Named-entity recognition | batch_69c6e7d4f3388190941f03fd80b0c223 |
completed | March 27, 2026, 8:25 p.m. |
| PD | Predicate disambiguation | batch_69c6e1c932888190b125ca3785b18553 |
completed | March 27, 2026, 8 p.m. |
Created at: March 27, 2026, 2:46 p.m.