Triple
T37652858
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | MTV 80s |
E937218
|
entity |
| Predicate | broadcastsMusicVideosFrom |
P110806
|
FINISHED |
| Object | MTV archives |
—
|
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: MTV archives | Statement: [MTV 80s, broadcastsMusicVideosFrom, MTV archives]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: broadcastsMusicVideosFrom Context triple: [MTV 80s, broadcastsMusicVideosFrom, MTV archives]
-
A.
musicVideoBroadcaster
Indicates that an entity broadcasts or transmits a particular music video to an audience or platform.
-
B.
musicVideoPlatform
Indicates a platform or service on which a music video is hosted, distributed, or made available for viewing.
-
C.
videoPlatform
Indicates a relationship where an entity serves as or is associated with a platform used for hosting, sharing, or streaming video content.
-
D.
broadcastsIn
Indicates that one entity transmits or airs content within a particular medium, channel, location, or time frame.
-
E.
musicVideoFrom
chosen
Indicates that a music video originates from, is derived from, or is associated with a particular source work or 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_69f76ed4fe908190b8061c5c135e0971 |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_69fbc36ce1f88190a7fa1656b714e107 |
completed | May 6, 2026, 10:40 p.m. |
| PD | Predicate disambiguation | batch_69fbbd166a488190b1bf9316b0790801 |
completed | May 6, 2026, 10:13 p.m. |
Created at: May 3, 2026, 4:18 p.m.