Triple
T28184216
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Kobe – Naha |
E716124
|
entity |
| Predicate | routeNameInJapanese |
P28734
|
FINISHED |
| Object | 神戸－那覇線 |
—
|
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: 神戸－那覇線 | Statement: [Kobe – Naha, routeNameInJapanese, 神戸－那覇線]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: routeNameInJapanese Context triple: [Kobe – Naha, routeNameInJapanese, 神戸－那覇線]
-
A.
hasNameInJapanese
chosen
Indicates that an entity is associated with a specific name expressed in the Japanese language.
-
B.
nameInJapaneseKana
Indicates that an entity’s name is written or represented using Japanese kana characters.
-
C.
eraNameInJapanese
Indicates the Japanese-language name used for a specific historical or calendar era.
-
D.
officialNameInRomaji
Indicates that an entity’s official name is written using the Roman alphabet (romaji) representation.
-
E.
hasOfficialNameInJapanese
Indicates that an entity has an official, formally recognized name expressed in the Japanese language.
- 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_69efd6b4fc5c81909dd88f01a8c2b35d |
completed | April 27, 2026, 9:35 p.m. |
| NER | Named-entity recognition | batch_69f65a6c900881908f18b61273d7bf8d |
completed | May 2, 2026, 8:11 p.m. |
| PD | Predicate disambiguation | batch_69f659ce58408190ba9e007b4810d4d0 |
completed | May 2, 2026, 8:08 p.m. |
Created at: April 27, 2026, 10:21 p.m.