Triple
T24781073
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Лаперу́зов пролив |
E619996
|
entity |
| Predicate | оригинальноеНазваниеНаЯпонском |
P29322
|
FINISHED |
| Object | 宗谷海峡 |
—
|
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: 宗谷海峡 | Statement: [Лаперу́зов пролив, оригинальноеНазваниеНаЯпонском, 宗谷海峡]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: оригинальноеНазваниеНаЯпонском Context triple: [Лаперу́зов пролив, оригинальноеНазваниеНаЯпонском, 宗谷海峡]
-
A.
hasNameInJapanese
Indicates that an entity is associated with a specific name expressed in the Japanese language.
-
B.
nameInOriginalLanguage
chosen
Indicates that an entity’s name is given in its original or native language form.
-
C.
hasOfficialNameInJapanese
Indicates that an entity has an official, formally recognized name expressed in the Japanese language.
-
D.
nameInJapaneseKana
Indicates that an entity’s name is written or represented using Japanese kana characters.
-
E.
originalTitleName
Indicates that one entity is the original or primary title name associated with another entity.
- 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_69e2fabdbe8c8190adbb9434b8636cad |
completed | April 18, 2026, 3:30 a.m. |
| NER | Named-entity recognition | batch_69f42d9000b8819081ea2605f3c193d6 |
completed | May 1, 2026, 4:35 a.m. |
| PD | Predicate disambiguation | batch_69f420f471a0819095a6cd24ed8f7476 |
completed | May 1, 2026, 3:41 a.m. |
Created at: April 18, 2026, 4:44 a.m.