Triple
T37881817
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Hertsa region |
E944886
|
entity |
| Predicate | transferYearApprox |
P201254
|
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: [Hertsa region, transferYearApprox, 1940]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: transferYearApprox Context triple: [Hertsa region, transferYearApprox, 1940]
-
A.
transitionYear
Indicates the specific year in which a change, shift, or transition from one state, condition, or phase to another occurs.
-
B.
relocationYear
Indicates the year in which an entity was moved or transferred from one location to another.
-
C.
crossYearApproximate
Indicates an approximate temporal relationship that spans across one or more calendar years, without specifying exact start or end dates.
-
D.
NiceTransferYear
Indicates that an entity’s transfer in a particular year is considered favorable, pleasant, or beneficial.
-
E.
tradeYear
Indicates the specific calendar year in which a trade or commercial transaction took place or was recorded.
- 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_69f76ef02668819089e7940c4001af5e |
completed | May 3, 2026, 3:51 p.m. |
| NER | Named-entity recognition | batch_69ffe12ee59c8190bc7da386e6d5332d |
completed | May 10, 2026, 1:36 a.m. |
| PD | Predicate disambiguation | batch_69ffe0a138bc8190a3d4b48cd579e985 |
completed | May 10, 2026, 1:34 a.m. |
| PDg | Predicate description generation | batch_69ffe12d61e0819098692270ab2625e3 |
completed | May 10, 2026, 1:36 a.m. |
Created at: May 3, 2026, 4:19 p.m.