Triple
T26790664
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Kitan Strait |
E670508
|
entity |
| Predicate | hasNameRomanized |
P164578
|
FINISHED |
| Object | Kitan Kaikyō |
—
|
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: Kitan Kaikyō | Statement: [Kitan Strait, hasNameRomanized, Kitan Kaikyō]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasNameRomanized Context triple: [Kitan Strait, hasNameRomanized, Kitan Kaikyō]
-
A.
nameInLanguageRomanization
chosen
Indicates that an entity’s name is represented in the romanized (Latin-script) form of a particular language.
-
B.
hasRomanizationOf
Indicates that one entity is a romanized representation (written in the Latin alphabet) of the other entity’s original script form.
-
C.
hangulNameRomanized
Indicates that an entity’s Korean Hangul name is represented in its romanized (Latin alphabet) form.
-
D.
hasRomanizationStandard
Indicates that an entity’s romanized form follows a specified romanization standard or system.
-
E.
hasNameInKanji
Indicates that an entity is associated with a specific written form of its name in Kanji 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_69eeb31d45f8819089f52ebdbc556218 |
completed | April 27, 2026, 12:51 a.m. |
| NER | Named-entity recognition | batch_69f7308a096081909d66a56f3c926806 |
completed | May 3, 2026, 11:24 a.m. |
| PD | Predicate disambiguation | batch_69f72a00c5f081908b6539d15baf4e12 |
completed | May 3, 2026, 10:57 a.m. |
Created at: April 27, 2026, 4:16 a.m.