Triple
T35039674
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Play-Tone Records |
E1011032
|
entity |
| Predicate | hasParentMedium |
P7961
|
FINISHED |
| Object | feature film |
—
|
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: feature film | Statement: [Play-Tone Records, hasParentMedium, feature film]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasParentMedium Context triple: [Play-Tone Records, hasParentMedium, feature film]
-
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.
hasParentMaterial
Indicates that one entity is derived from, formed in, or directly associated with another entity that serves as its original or underlying material.
-
C.
hasParentUnit
Indicates that one unit is hierarchically contained within or belongs to another, higher-level unit.
-
D.
hasParentAlbumType
Indicates that an album is associated with a broader or more general album type from which it derives or is categorized.
-
E.
hasPageMedium
Indicates that a page or document is associated with a particular physical or digital medium through which it is presented or stored.
- 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_69f76dcea02c81908542a223f6d5059f |
completed | May 3, 2026, 3:46 p.m. |
| NER | Named-entity recognition | batch_69ffada24d188190a576a02dc280a7fb |
completed | May 9, 2026, 9:56 p.m. |
| PD | Predicate disambiguation | batch_69ffad46d6ac819081772f408b1389d5 |
completed | May 9, 2026, 9:55 p.m. |
Created at: May 3, 2026, 4:01 p.m.