Triple
T30348909
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | エンジェルビーツ |
E771936
|
entity |
| Predicate | 放送局 |
P147832
|
FINISHED |
| Object | TOKYO MX |
—
|
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: TOKYO MX | Statement: [エンジェルビーツ, 放送局, TOKYO MX]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: 放送局 Context triple: [エンジェルビーツ, 放送局, TOKYO MX]
-
A.
broadcastStation
chosen
Indicates that one entity functions as a broadcast station that transmits content or signals to an audience or network.
-
B.
broadcastNetwork
Indicates that one entity serves as the television or radio network that broadcasts the programming or content of another entity.
-
C.
hasBroadcastingInstitution
Indicates that one entity serves as the broadcasting institution (e.g., TV/radio/online broadcaster) responsible for transmitting or airing the content or service of another entity.
-
D.
broadcastFacilities
Indicates that one entity provides or is equipped with the means to transmit or distribute broadcasts (such as radio, television, or digital signals) to an audience.
-
E.
broadcastingWork
Indicates that one entity is a broadcasted work (such as a radio or TV program) that is transmitted or made available to an audience by 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_69f2248b9a208190bc3e6804acd5afd6 |
completed | April 29, 2026, 3:32 p.m. |
| NER | Named-entity recognition | batch_69f6820a250c8190ba7afa43f6f55c46 |
completed | May 2, 2026, 11 p.m. |
| PD | Predicate disambiguation | batch_69f678ce54b081908c26edfd49e39c60 |
completed | May 2, 2026, 10:21 p.m. |
Created at: April 29, 2026, 7:56 p.m.