Triple
T19486071
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Rēzekne, Latvian SSR, Soviet Union |
E487514
|
entity |
| Predicate | timeExistenceStarted |
P10897
|
FINISHED |
| Object | 1940 |
—
|
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: 1940 | Statement: [Rēzekne, Latvian SSR, Soviet Union, timeExistenceStarted, 1940]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: timeExistenceStarted Context triple: [Rēzekne, Latvian SSR, Soviet Union, timeExistenceStarted, 1940]
-
A.
timeExistence
Indicates the period or duration during which an entity exists or is valid.
-
B.
timeStartApprox
Indicates that the associated event or state begins at an approximate, rather than exact, point in time.
-
C.
timeSpanOfCreation
Indicates the period of time during which the creation of an entity took place.
-
D.
hasTimeStart
chosen
Indicates that an event, process, or state begins at a specific point in time.
-
E.
timePeriodOrigin
Indicates that one entity is the time period in which the other entity originated or first came into existence.
- 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_69d8e8d924388190b847cb15bb3d0aff |
completed | April 10, 2026, 12:11 p.m. |
| NER | Named-entity recognition | batch_69e6343f46e88190b7ba65c210285bee |
completed | April 20, 2026, 2:12 p.m. |
| PD | Predicate disambiguation | batch_69e4fd7883308190b73912a71a35a835 |
completed | April 19, 2026, 4:06 p.m. |
Created at: April 10, 2026, 1:39 p.m.