Triple
T14414924
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Kalinin Oblast |
E357423
|
entity |
| Predicate | existedFromTo |
P114164
|
FINISHED |
| Object | 1935–1990 |
—
|
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: 1935–1990 | Statement: [Kalinin Oblast, existedFromTo, 1935–1990]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: existedFromTo Context triple: [Kalinin Oblast, existedFromTo, 1935–1990]
-
A.
existedAfter
Indicates that one entity came into existence only after another entity already existed.
-
B.
existedUntil
Indicates that an entity continued to exist up to, but not necessarily beyond, a specified time or event.
-
C.
existedAs
Indicates that one entity had the status, form, or identity of another entity during a certain time or context.
-
D.
existedBeforeEvent
Indicates that the subject entity was already in existence prior to the occurrence of the specified event.
-
E.
existedUnder
Indicates that one entity existed within the authority, jurisdiction, or domain of another entity during a certain period.
- F. None of above. chosen
Provenance (4 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_69d82793421c8190861eb0e673b085de |
completed | April 9, 2026, 10:26 p.m. |
| NER | Named-entity recognition | batch_69de90cc99208190a2313b1acfb5d802 |
completed | April 14, 2026, 7:09 p.m. |
| PD | Predicate disambiguation | batch_69de5c30467881908e770e3940295641 |
completed | April 14, 2026, 3:24 p.m. |
| PDg | Predicate description generation | batch_69de5fb4de14819092acdecbd201d672 |
completed | April 14, 2026, 3:39 p.m. |
Created at: April 10, 2026, 1:17 a.m.