Triple
T24076681
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Gim |
E596380
|
entity |
| Predicate | standardRomanizationInSouthKorea |
P23170
|
FINISHED |
| Object | Gim |
—
|
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: Gim | Statement: [Gim, standardRomanizationInSouthKorea, Gim]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: standardRomanizationInSouthKorea Context triple: [Gim, standardRomanizationInSouthKorea, Gim]
-
A.
hangulNameRomanized
Indicates that an entity’s Korean Hangul name is represented in its romanized (Latin alphabet) form.
-
B.
hasRomanizationStandard
chosen
Indicates that an entity’s romanized form follows a specified romanization standard or system.
-
C.
romanizationStandardReplacedBy
Indicates that one system or convention for romanization has been superseded and replaced by another romanization standard.
-
D.
romanizationType
Indicates the specific system or method used to convert text from one writing system into its Roman (Latin) alphabet representation.
-
E.
romanizationVariantOf
Indicates that one written form is a different romanized representation of the same underlying word or expression as another.
- 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_69e288c3999c8190809b282a04813dec |
completed | April 17, 2026, 7:23 p.m. |
| NER | Named-entity recognition | batch_69f1db1e959c81909f4365b5d7f934d9 |
completed | April 29, 2026, 10:19 a.m. |
| PD | Predicate disambiguation | batch_69f1764b1d4c8190b12590c6339c31c1 |
completed | April 29, 2026, 3:08 a.m. |
Created at: April 17, 2026, 10:42 p.m.