Triple
T21974113
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Pyongyang Broadcasting Station |
E542660
|
entity |
| Predicate | typeOfStation |
P27765
|
FINISHED |
| Object | external service broadcaster |
—
|
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: external service broadcaster | Statement: [Pyongyang Broadcasting Station, typeOfStation, external service broadcaster]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: typeOfStation Context triple: [Pyongyang Broadcasting Station, typeOfStation, external service broadcaster]
-
A.
stationType
chosen
Indicates the specific category or classification of a station based on its function, services, or operational characteristics.
-
B.
servesStationType
Indicates that an entity provides service to, or operates in connection with, a particular type or category of station.
-
C.
railwayStationCategory
Indicates the classification or type category assigned to a railway station within a rail network or system.
-
D.
ownedStation
Indicates that one entity possesses ownership or control over a particular station.
-
E.
operatedStation
Indicates that one entity managed, ran, or was responsible for the operation of a particular station.
- 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_69e0c48070988190909db97667b9a0ac |
completed | April 16, 2026, 11:14 a.m. |
| NER | Named-entity recognition | batch_69f1248668ac81909c74b2be62f69fce |
completed | April 28, 2026, 9:20 p.m. |
| PD | Predicate disambiguation | batch_69e6f6154e408190acc5b2c278acaff4 |
completed | April 21, 2026, 3:59 a.m. |
Created at: April 16, 2026, 8:03 p.m.