Triple
T30277348
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Toyohara |
E769987
|
entity |
| Predicate | changedNameAfter |
P169384
|
FINISHED |
| Object | Soviet occupation of southern Sakhalin |
—
|
NE NERFINISHED |
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: Soviet occupation of southern Sakhalin | Statement: [Toyohara, changedNameAfter, Soviet occupation of southern Sakhalin]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: changedNameAfter Context triple: [Toyohara, changedNameAfter, Soviet occupation of southern Sakhalin]
-
A.
changedNameIn
Indicates that an entity has altered or adopted a different name within a specific context, time period, or jurisdiction.
-
B.
changedNameOn
Indicates that an entity altered or updated its name at a specific point in time or on a particular date.
-
C.
changedNameBy
Indicates that one entity altered or updated the name of another entity.
-
D.
changedNameInHonorOf
Indicates that an entity altered its name specifically to honor or pay tribute to another entity.
-
E.
changedSurnameTo
Indicates that an entity has adopted a new surname, replacing their previous one, with the new surname specified as the related 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_69f224868fa8819099127eaf8855a28f |
completed | April 29, 2026, 3:32 p.m. |
| NER | Named-entity recognition | batch_69f680d983608190a05ee341096d3c6c |
completed | May 2, 2026, 10:55 p.m. |
| PD | Predicate disambiguation | batch_69f678ce54b081908c26edfd49e39c60 |
completed | May 2, 2026, 10:21 p.m. |
| PDg | Predicate description generation | batch_69f67d31cc60819084f64bd056e1ea4d |
completed | May 2, 2026, 10:39 p.m. |
Created at: April 29, 2026, 7:44 p.m.