Triple
T14506828
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Nonsan |
E340283
|
entity |
| Predicate | telephonyAreaCode |
P190
|
FINISHED |
| Object | South Korean area code for South Chungcheong region |
—
|
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: South Korean area code for South Chungcheong region | Statement: [Nonsan, telephonyAreaCode, South Korean area code for South Chungcheong region]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: telephonyAreaCode Context triple: [Nonsan, telephonyAreaCode, South Korean area code for South Chungcheong region]
-
A.
areaCode
Indicates that a location, phone number, or region is associated with a specific telephone area code.
-
B.
hasAreaCode
chosen
Indicates that a specified telephone area code is assigned to or associated with a particular geographic region, location, or phone service entity.
-
C.
hasAreaCodeCountry
Indicates that a particular telephone area code is associated with or belongs to a specific country.
-
D.
hasAreaCodeType
Indicates that an entity’s area code is associated with a specific type or classification of area code.
-
E.
callingCode
Indicates the telephone country or area code associated with an entity for making phone calls.
- 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_69d822d9c0408190b9a2b3643e58bb4d |
completed | April 9, 2026, 10:06 p.m. |
| NER | Named-entity recognition | batch_69de94e40e44819084f323f8f9982b75 |
completed | April 14, 2026, 7:26 p.m. |
| PD | Predicate disambiguation | batch_69de5c4ccba08190a988bfda0bc9f5cb |
completed | April 14, 2026, 3:25 p.m. |
Created at: April 10, 2026, 1:21 a.m.