Triple
T23138613
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | .kr |
E577393
|
entity |
| Predicate | reservedForGovernmentUse |
P24110
|
FINISHED |
| Object | .go.kr |
—
|
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: .go.kr | Statement: [.kr, reservedForGovernmentUse, .go.kr]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: reservedForGovernmentUse Context triple: [.kr, reservedForGovernmentUse, .go.kr]
-
A.
reservedFor
Indicates that something is set aside or allocated specifically for the use, benefit, or purpose of a particular entity or group.
-
B.
usedInGovernmentIn
Indicates that something is employed, applied, or functions within the context of a specific government or governmental system.
-
C.
recognizedGovernment
Indicates that one entity formally acknowledges another entity as the legitimate governing authority of a state or territory.
-
D.
usedForAdministrativePurposes
Indicates that something is employed in managing, organizing, or overseeing official, institutional, or organizational activities and records.
-
E.
hasOfficialUse
chosen
Indicates that something is used in an authorized or formally recognized capacity, typically by an official body or for official purposes.
- 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_69e245f8e6248190ba3d58e068b4dccb |
completed | April 17, 2026, 2:38 p.m. |
| NER | Named-entity recognition | batch_69f18e8e23988190814524f63a7efe36 |
completed | April 29, 2026, 4:52 a.m. |
| PD | Predicate disambiguation | batch_69ef89f83b108190aaaa1db6221fc163 |
completed | April 27, 2026, 4:08 p.m. |
Created at: April 17, 2026, 4 p.m.