Triple
T24467847
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Tokyo Broadcasting Station |
E617018
|
entity |
| Predicate | publicBroadcastingPrecursor |
P156213
|
FINISHED |
| Object | NHK |
—
|
NE NERFINISHED |
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: NHK | Statement: [Tokyo Broadcasting Station, publicBroadcastingPrecursor, NHK]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: publicBroadcastingPrecursor Context triple: [Tokyo Broadcasting Station, publicBroadcastingPrecursor, NHK]
-
A.
originallyBroadcastIn
Indicates that a broadcast (such as a TV or radio program) was first aired in a particular country, region, or market.
-
B.
broadcastFor
Indicates that one entity transmits or disseminates content, information, or a signal on behalf of, or in service of, another entity.
-
C.
broadcastAfter
Indicates that one broadcast event occurs later in time than another broadcast event.
-
D.
primaryBroadcaster
Indicates that one entity serves as the main or principal broadcaster for another entity (such as an event, program, or channel).
-
E.
firstBroadcastFor
Indicates that one entity is the initial or earliest broadcast instance associated with another entity (such as a program, episode, or event).
- 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_69e2d7f197588190889a03e620558059 |
completed | April 18, 2026, 1:01 a.m. |
| NER | Named-entity recognition | batch_69f299413ea88190b15e482035ff5a83 |
completed | April 29, 2026, 11:50 p.m. |
| PD | Predicate disambiguation | batch_69f287d76c7c81909494f12e606a9149 |
completed | April 29, 2026, 10:36 p.m. |
| PDg | Predicate description generation | batch_69f28f4d978c81908310c01def2514cc |
completed | April 29, 2026, 11:07 p.m. |
Created at: April 18, 2026, 2:20 a.m.