Triple
T18935047
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Nippon Television Holdings, Inc. |
E463220
|
entity |
| Predicate | languageOfBroadcastContent |
P3314
|
FINISHED |
| Object | Japanese |
—
|
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: Japanese | Statement: [Nippon Television Holdings, Inc., languageOfBroadcastContent, Japanese]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: languageOfBroadcastContent Context triple: [Nippon Television Holdings, Inc., languageOfBroadcastContent, Japanese]
-
A.
languageOfPrimaryBroadcasts
chosen
Indicates the language in which an entity’s primary broadcasts are delivered.
-
B.
languageSpokenOnScreen
Indicates that a particular language is used in spoken dialogue or audible communication within an on-screen work (such as a film, show, or video).
-
C.
broadcastInLanguage
Indicates that a broadcast, program, or media content is transmitted or made available in a specified language.
-
D.
contentLanguage
Indicates the language in which the content is expressed or intended to be understood.
-
E.
languageOfTransmission
Indicates the language used to convey or transmit the content or information in a given communication or resource.
- 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_69d8dcfec90481909e926be9767e5779 |
completed | April 10, 2026, 11:20 a.m. |
| NER | Named-entity recognition | batch_69e5d3e6a8208190973669cae439a91e |
completed | April 20, 2026, 7:21 a.m. |
| PD | Predicate disambiguation | batch_69e4a2efec5c8190840704016bf547a1 |
completed | April 19, 2026, 9:40 a.m. |
Created at: April 10, 2026, 11:59 a.m.