Triple
T6320951
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Kholmsk |
E141734
|
entity |
| Predicate | wasUnderJapaneseControlUntil |
P70035
|
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: [Kholmsk, wasUnderJapaneseControlUntil, 1945]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: wasUnderJapaneseControlUntil Context triple: [Kholmsk, wasUnderJapaneseControlUntil, 1945]
-
A.
JapaneseOccupationStart
Indicates the point in time when a Japanese occupation of a place or population begins.
-
B.
administrativeStatusDuringJapaneseRule
Indicates the administrative status or classification an entity held under Japanese colonial rule during the specified period.
-
C.
yearOfSurrender
Indicates the specific calendar year in which an entity formally surrendered or yielded, typically ending its resistance or control.
-
D.
countryOccupied
Indicates that one country has taken control of and is occupying the territory of another country, typically through military or coercive means.
-
E.
wasProtectorateOf
Indicates that one entity was formerly under the protection and partial control of another, typically more powerful, entity.
- 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_69c008d13b8c8190be47d896eb735605 |
completed | March 22, 2026, 3:20 p.m. |
| NER | Named-entity recognition | batch_69c064c61f008190b316b9ff1023b057 |
completed | March 22, 2026, 9:53 p.m. |
| PD | Predicate disambiguation | batch_69c060e5efc48190861b8266e5b0cc0c |
completed | March 22, 2026, 9:36 p.m. |
| PDg | Predicate description generation | batch_69c0623bb29081908bfdfb84a07ece90 |
completed | March 22, 2026, 9:42 p.m. |
Created at: March 22, 2026, 4:29 p.m.