Triple
T2289769
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Mickey Mouse Club (1993 TV series) |
E51474
|
entity |
| Predicate | hasMainMedium |
P7961
|
FINISHED |
| Object | television |
—
|
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: television | Statement: [Mickey Mouse Club (1993 TV series), hasMainMedium, television]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasMainMedium Context triple: [Mickey Mouse Club (1993 TV series), hasMainMedium, television]
-
A.
hasAssociatedMedium
chosen
Indicates that one entity is linked to another entity that serves as its medium, format, or channel of expression or transmission.
-
B.
hasPageMedium
Indicates that a page or document is associated with a particular physical or digital medium through which it is presented or stored.
-
C.
hasMainOrgan
Indicates that an entity possesses a primary or principal organ that plays a central role in its biological or functional system.
-
D.
hasCommonMedia
Indicates that two entities share at least one media item (such as an image, video, or audio file) in common.
-
E.
hasMainImageSource
Indicates that an entity is associated with a primary image file or URL that serves as its main visual representation.
- 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_69a88b09c644819090b503456d96bf70 |
completed | March 4, 2026, 7:42 p.m. |
| NER | Named-entity recognition | batch_69abc273b67c8190bcd96f9a484647ef |
completed | March 7, 2026, 6:15 a.m. |
| PD | Predicate disambiguation | batch_69abbdbc8bcc8190a183481d766965a4 |
completed | March 7, 2026, 5:55 a.m. |
Created at: March 4, 2026, 7:48 p.m.