Triple
T10617238
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Eumseong County |
E276151
|
entity |
| Predicate | hasNativeNameScript |
P63723
|
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: [Eumseong County, hasNativeNameScript, 음성군]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasNativeNameScript Context triple: [Eumseong County, hasNativeNameScript, 음성군]
-
A.
hasUnicodeScript
Indicates that a character or text element belongs to a specific Unicode script category (such as Latin, Cyrillic, or Han).
-
B.
nativeNameScript
chosen
Indicates the writing system or script in which an entity’s native name is expressed.
-
C.
hasNameInTeluguScript
Indicates that an entity is associated with a name written in the Telugu script.
-
D.
associatedLanguageScript
Indicates that there is a relationship between a language and the script or writing system used to represent it.
-
E.
hasUnicodeName
Indicates that an entity is associated with a specific official Unicode name assigned to a character or symbol.
- 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_69d6aaf948d88190806cc3a8c47a3fb2 |
completed | April 8, 2026, 7:22 p.m. |
| NER | Named-entity recognition | batch_69d6df6e2df4819099a19b59d90d0dd1 |
completed | April 8, 2026, 11:06 p.m. |
| PD | Predicate disambiguation | batch_69d6dd7a223c8190854409d76368f3e8 |
completed | April 8, 2026, 10:58 p.m. |
Created at: April 8, 2026, 7:33 p.m.