Triple
T25962654
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Rungna Island |
E645581
|
entity |
| Predicate | hasNameInMcCuneReischauer |
P78997
|
FINISHED |
| Object | Rŭngna-sŏm |
—
|
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: Rŭngna-sŏm | Statement: [Rungna Island, hasNameInMcCuneReischauer, Rŭngna-sŏm]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasNameInMcCuneReischauer Context triple: [Rungna Island, hasNameInMcCuneReischauer, Rŭngna-sŏm]
-
A.
nameInMcCuneReischauer
chosen
Indicates that an entity’s name is represented using the McCune–Reischauer romanization system.
-
B.
hasNameInKanji
Indicates that an entity is associated with a specific written form of its name in Kanji characters.
-
C.
hasNameInJapanese
Indicates that an entity is associated with a specific name expressed in the Japanese language.
-
D.
hasOkinawanName
Indicates that an entity possesses a specific name in the Okinawan language.
-
E.
nameInJapaneseKana
Indicates that an entity’s name is written or represented using Japanese kana characters.
- 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_69e77e85efc08190997da7fcf98bd300 |
completed | April 21, 2026, 1:41 p.m. |
| NER | Named-entity recognition | batch_69f68f670b608190a0b6ab60d722b4e0 |
completed | May 2, 2026, 11:57 p.m. |
| PD | Predicate disambiguation | batch_69f68b78f29481908cc8f390496dee97 |
completed | May 2, 2026, 11:40 p.m. |
Created at: April 22, 2026, 8:47 a.m.