Triple
T1419893
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Yugtun |
E30199
|
entity |
| Predicate | hasMediaIn |
P7961
|
FINISHED |
| Object | radio 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: radio broadcasts | Statement: [Yugtun, hasMediaIn, radio broadcasts]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasMediaIn Context triple: [Yugtun, hasMediaIn, radio broadcasts]
-
A.
hasCommonMedia
Indicates that two entities share at least one media item (such as an image, video, or audio file) in common.
-
B.
hasAssociatedMedium
chosen
Indicates that one entity is linked to another entity that serves as its medium, format, or channel of expression or transmission.
-
C.
hasLocalMedia
Indicates that an entity is associated with media content that is stored or available locally rather than from a remote source.
-
D.
hasMediaHub
Indicates that one entity possesses, contains, or is associated with a central platform or facility for managing, distributing, or accessing media content.
-
E.
hasHomeMediaRelease
Indicates that a work has been released in a home media format (such as DVD, Blu-ray, or digital home release).
- 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_69a498fb823c8190a67ce4c4837e641a |
completed | March 1, 2026, 7:52 p.m. |
| NER | Named-entity recognition | batch_69a4c40764ec8190b85de6befcb20dda |
completed | March 1, 2026, 10:56 p.m. |
| PD | Predicate disambiguation | batch_69a4bf060b0081909ba00e6ac093a28b |
completed | March 1, 2026, 10:34 p.m. |
Created at: March 1, 2026, 7:59 p.m.