Triple
T8525609
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 북구 |
E201807
|
entity |
| Predicate | hasNameInHangul |
P17869
|
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: [북구, hasNameInHangul, 북구]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasNameInHangul Context triple: [북구, hasNameInHangul, 북구]
-
A.
nameInKorean
chosen
Indicates that an entity’s name is expressed in the Korean language.
-
B.
hasNameInJapanese
Indicates that an entity is associated with a specific name expressed in the Japanese language.
-
C.
hanjaName
Indicates that one entity is the Sino-Korean (hanja) written form corresponding to the name of another entity.
-
D.
hasUnicodeName
Indicates that an entity is associated with a specific official Unicode name assigned to a character or symbol.
-
E.
hasJavaneseName
Indicates that an entity possesses a name expressed in the Javanese 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_69ca83228b24819085d22e7dc99f5d94 |
completed | March 30, 2026, 2:05 p.m. |
| NER | Named-entity recognition | batch_69cbe6463fe48190b6d3482212356be1 |
completed | March 31, 2026, 3:20 p.m. |
| PD | Predicate disambiguation | batch_69cbd10f64b4819080859057c19e58f0 |
completed | March 31, 2026, 1:50 p.m. |
Created at: March 30, 2026, 6:16 p.m.