Triple
T33750567
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Intimate Moments for a Sensual Evening |
E864829
|
entity |
| Predicate | availableOnFormat |
P102437
|
FINISHED |
| Object | DVD |
—
|
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: DVD | Statement: [Intimate Moments for a Sensual Evening, availableOnFormat, DVD]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: availableOnFormat Context triple: [Intimate Moments for a Sensual Evening, availableOnFormat, DVD]
-
A.
appearsInFilmFormat
Indicates that something is presented or occurs within a specific film format or medium of cinematic presentation.
-
B.
mayBeAvailableIn
Indicates that an entity has the potential to be obtainable, accessible, or present within a specified context, location, or medium.
-
C.
presentedInFormat
chosen
Indicates that something is expressed, delivered, or made available using a particular format or representation.
-
D.
operatesInFormat
Indicates that an entity functions, performs its role, or is carried out using a specified format.
-
E.
soldAtFormat
Indicates that an item is sold in a particular format or packaging type.
- 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_69f3498c35f881909df279ae4270f831 |
completed | April 30, 2026, 12:22 p.m. |
| NER | Named-entity recognition | batch_69f6fb8f45648190be048a167b9fd1c6 |
completed | May 3, 2026, 7:38 a.m. |
| PD | Predicate disambiguation | batch_69f6f96ea0c08190902a3d0e1f263e8c |
completed | May 3, 2026, 7:29 a.m. |
Created at: May 1, 2026, 1:45 a.m.