Triple
T30458646
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Benny Young |
E774932
|
entity |
| Predicate | appearsOnMedium |
P54385
|
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: [Benny Young, appearsOnMedium, television]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: appearsOnMedium Context triple: [Benny Young, appearsOnMedium, television]
-
A.
occursInMedium
chosen
Indicates that an event, process, or interaction takes place within or is hosted by a particular medium or environment.
-
B.
applicableMedium
Indicates that a particular medium or material is suitable for use with, or can be effectively applied by, the referenced entity.
-
C.
representsMedium
Indicates that one entity serves as the medium, channel, or means through which another entity is expressed, communicated, or realized.
-
D.
basedOnMedium
Indicates that one entity is derived from, adapted from, or created using another entity as its source medium or foundational material.
-
E.
mayAppearOn
Indicates that one entity is allowed or able to be shown, featured, or present on another entity (such as a platform, medium, or surface).
- 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_69f22494fb60819095d893de0284f886 |
completed | April 29, 2026, 3:32 p.m. |
| NER | Named-entity recognition | batch_69f7cec454a88190a9f3bbee2b856636 |
completed | May 3, 2026, 10:40 p.m. |
| PD | Predicate disambiguation | batch_69f7c8977c288190997a892ec5f756ed |
completed | May 3, 2026, 10:13 p.m. |
Created at: April 29, 2026, 8:10 p.m.