Triple
T25183863
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ad Vitam Distribution |
E630660
|
entity |
| Predicate | scopeOfReleases |
P158005
|
FINISHED |
| Object | home video distribution |
—
|
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: home video distribution | Statement: [Ad Vitam Distribution, scopeOfReleases, home video distribution]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: scopeOfReleases Context triple: [Ad Vitam Distribution, scopeOfReleases, home video distribution]
-
A.
scopeOfReleases
chosen
Indicates the range, extent, or boundaries within which releases (such as versions, updates, or publications) are applicable or intended to take effect.
-
B.
releases
Indicates that one entity causes something to be set free, emitted, or made available from its control or containment.
-
C.
hasScheduledReleases
Indicates that an entity has one or more releases planned to occur at specific future times.
-
D.
eraOfWorkRelease
Indicates the historical or cultural era during which a work was originally released.
-
E.
releasesInclude
Indicates that a particular release or distribution contains, bundles, or makes available the specified component, item, or content.
- 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_69e75a88fdf081908e47ae6e195c14e1 |
completed | April 21, 2026, 11:07 a.m. |
| NER | Named-entity recognition | batch_69f46dc920e88190874a516646bf4ff5 |
completed | May 1, 2026, 9:09 a.m. |
| PD | Predicate disambiguation | batch_69f45cfb53f4819099bba48c5057e787 |
completed | May 1, 2026, 7:57 a.m. |
Created at: April 21, 2026, 12:36 p.m.