Triple
T27691115
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Paranoimia (Max Headroom version) |
E698159
|
entity |
| Predicate | musicVideoFeaturesCharacter |
P3289
|
FINISHED |
| Object | Max Headroom |
—
|
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: Max Headroom | Statement: [Paranoimia (Max Headroom version), musicVideoFeaturesCharacter, Max Headroom]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: musicVideoFeaturesCharacter Context triple: [Paranoimia (Max Headroom version), musicVideoFeaturesCharacter, Max Headroom]
-
A.
musicVideoFeatures
chosen
Indicates that a music video includes or prominently showcases a particular person, group, or element.
-
B.
musicVideoCharacterName
Indicates that the predicate specifies the name of a character appearing in a music video.
-
C.
hasMusicVideoCharacteristic
Indicates that a music video possesses a specific attribute, feature, or quality.
-
D.
musicVideoRotation
Indicates the frequency or schedule with which a music video is played or broadcast within a given programming rotation.
-
E.
musicVideoDescription
Indicates that one entity is a textual description or summary of the content of a music video associated with 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_69ef590df8708190af5488f0638e790c |
completed | April 27, 2026, 12:39 p.m. |
| NER | Named-entity recognition | batch_69f6a28c7c148190bfc980aad9f678ca |
completed | May 3, 2026, 1:19 a.m. |
| PD | Predicate disambiguation | batch_69f69fe1e3c88190830bb2e9f407357e |
completed | May 3, 2026, 1:07 a.m. |
Created at: April 27, 2026, 2:51 p.m.