Triple
T31664833
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Northwest South Korea |
E808096
|
entity |
| Predicate | communicationsStandard |
P174109
|
FINISHED |
| Object | Seoul-based standard Korean in official contexts |
—
|
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: Seoul-based standard Korean in official contexts | Statement: [Northwest South Korea, communicationsStandard, Seoul-based standard Korean in official contexts]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: communicationsStandard Context triple: [Northwest South Korea, communicationsStandard, Seoul-based standard Korean in official contexts]
-
A.
communicationMode
Indicates the method or channel through which communication between entities is carried out.
-
B.
communicationModel
Indicates the type or framework of communication used or assumed in the relationship between entities.
-
C.
communicationService
Indicates a relationship where one entity provides or facilitates a means for another entity to exchange information or messages.
-
D.
communicationPrinciple
Indicates a guiding rule or norm that shapes how communication should be conducted between entities.
-
E.
communicationUnderstoodBy
Indicates that a communicated message or information is successfully comprehended by the receiving entity.
- F. None of above. chosen
Provenance (4 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_69f348dbeef4819080b446a7feb6340b |
completed | April 30, 2026, 12:19 p.m. |
| NER | Named-entity recognition | batch_69f6bcc425588190afd0dceba43ed79f |
completed | May 3, 2026, 3:11 a.m. |
| PD | Predicate disambiguation | batch_69f6ba6cef208190bc5cd43d96127004 |
completed | May 3, 2026, 3:01 a.m. |
| PDg | Predicate description generation | batch_69f6bbbe23d48190b2aa662d69b41900 |
completed | May 3, 2026, 3:06 a.m. |
Created at: April 30, 2026, 10:58 p.m.