Triple
T24334302
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | NHK World Premium |
E613334
|
entity |
| Predicate | programSource |
P40940
|
FINISHED |
| Object | NHK General TV |
—
|
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 General TV | Statement: [NHK World Premium, programSource, NHK General TV]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: programSource Context triple: [NHK World Premium, programSource, NHK General TV]
-
A.
scriptSource
Indicates that one entity is the origin or provider of the script used or referenced by another entity.
-
B.
typicalProgrammingSource
chosen
Indicates that one entity is a common or standard source from which the other entity obtains programming content or code.
-
C.
program
Indicates that an entity creates, writes, or develops a computer program or software application.
-
D.
programDocument
Indicates that a document is associated with, defines, or describes a particular program (such as a software application, project, or initiative).
-
E.
programGeneration
Indicates that one entity creates, writes, or produces a program (such as software or code) for or on behalf of another entity.
- 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_69e2d7dcc5a08190b53691130d56cbc4 |
completed | April 18, 2026, 1:01 a.m. |
| NER | Named-entity recognition | batch_69f292f444b08190b9c8e033ff6ee5fc |
completed | April 29, 2026, 11:23 p.m. |
| PD | Predicate disambiguation | batch_69f287ad30048190b3ad3613486f277f |
completed | April 29, 2026, 10:35 p.m. |
Created at: April 18, 2026, 1:56 a.m.