Triple
T37914772
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | South Korean media |
E945784
|
entity |
| Predicate | hasMajorOutlet |
P121165
|
FINISHED |
| Object | KBS |
E587045
|
NE 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: KBS | Statement: [South Korean media, hasMajorOutlet, KBS]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasMajorOutlet Context triple: [South Korean media, hasMajorOutlet, KBS]
-
A.
isMajorOutletIn
Indicates that an outlet (such as a store, branch, or distribution point) is a primary or significant presence within a specified geographic area or market.
-
B.
hasOutlet
Indicates that one entity provides, contains, or is equipped with an outlet or point of access for another entity.
-
C.
hasMajorOutflowBasin
Indicates that a geographic feature (such as a water body or watershed) has a specific basin into which most or all of its water ultimately flows.
-
D.
majorOutletOf
Indicates that one entity serves as a primary distribution or sales channel for another entity’s products or services.
-
E.
majorOutlet
chosen
Indicates that an entity functions as a primary or significant distribution or publication channel for another entity.
- F. None of above.
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_69f76ef2ebd88190be5229f2621070b3 |
completed | May 3, 2026, 3:51 p.m. |
| NER | Named-entity recognition | batch_6a037c903be48190a2fafa53d7d50d42 |
completed | May 12, 2026, 7:16 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a410cd0af788190879149a313b7c40f |
completed | June 28, 2026, noon |
| PD | Predicate disambiguation | batch_6a037a192a008190a9917688a9e804f4 |
completed | May 12, 2026, 7:06 p.m. |
Created at: May 3, 2026, 4:20 p.m.