Triple
T6570251
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | NHK-FM |
E155414
|
entity |
| Predicate | notableContentType |
P71926
|
FINISHED |
| Object | live concert broadcasts |
—
|
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: live concert broadcasts | Statement: [NHK-FM, notableContentType, live concert broadcasts]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: notableContentType Context triple: [NHK-FM, notableContentType, live concert broadcasts]
-
A.
notableTargetType
Indicates that the subject is notable or significant specifically in relation to entities of the given target type.
-
B.
notableFormat
Indicates that something is particularly recognized or distinguished for being in a specific format.
-
C.
notableText
Indicates that a particular piece of text is especially significant, prominent, or worthy of attention in relation to the associated entity or context.
-
D.
notableCover
Indicates that one entity is a particularly well-known or significant cover version or adaptation of another entity.
-
E.
notableElement
Indicates that an entity has a component, feature, or part that is especially significant, prominent, or noteworthy in relation to it.
- 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_69c688151254819080387f87deab8fa7 |
completed | March 27, 2026, 1:37 p.m. |
| NER | Named-entity recognition | batch_69c6cc9c6cb0819084fec8e0beb430de |
completed | March 27, 2026, 6:29 p.m. |
| PD | Predicate disambiguation | batch_69c6acf93cb48190b54f5dd6febd34dc |
completed | March 27, 2026, 4:14 p.m. |
| PDg | Predicate description generation | batch_69c6cc988c0081909d22b86ca299331c |
completed | March 27, 2026, 6:29 p.m. |
Created at: March 27, 2026, 1:53 p.m.