Triple
T6012128
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Polish–Slovak border |
E133859
|
entity |
| Predicate | redefinedInYear |
P28840
|
FINISHED |
| Object | 1945 |
—
|
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: 1945 | Statement: [Polish–Slovak border, redefinedInYear, 1945]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: redefinedInYear Context triple: [Polish–Slovak border, redefinedInYear, 1945]
-
A.
redefinitionYear
chosen
Indicates the year in which something was redefined, such as when its definition, scope, or formal status was officially changed.
-
B.
replacedInYear
Indicates that one entity took the place of or superseded another entity in a specific calendar year.
-
C.
renamedYear
Indicates the year in which an entity underwent a renaming or change of name.
-
D.
reintroducedInYear
Indicates that an entity, previously absent or discontinued, was brought back or reinstated in a specified year.
-
E.
recastInYear
Indicates that an existing work, role, or production was cast again with different performers in a specified year.
- 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_69c0087361a48190905c6b55969852b8 |
completed | March 22, 2026, 3:19 p.m. |
| NER | Named-entity recognition | batch_69c04f5159bc8190a988293bbbb99d24 |
completed | March 22, 2026, 8:21 p.m. |
| PD | Predicate disambiguation | batch_69c049e4daf4819099bf870dc700e0a2 |
completed | March 22, 2026, 7:58 p.m. |
Created at: March 22, 2026, 4:06 p.m.