Triple
T5530424
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | MCA Home Video |
E145032
|
entity |
| Predicate | typicalReleaseWindow |
P64754
|
FINISHED |
| Object | post-theatrical home video release |
—
|
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: post-theatrical home video release | Statement: [MCA Home Video, typicalReleaseWindow, post-theatrical home video release]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: typicalReleaseWindow Context triple: [MCA Home Video, typicalReleaseWindow, post-theatrical home video release]
-
A.
rankingReleasePeriod
Indicates the time span or date range during which a particular ranking is valid, published, or in effect.
-
B.
wideReleaseDate
Indicates the date on which a work (such as a film) is first made widely available to the general public across many locations or markets.
-
C.
typicalStartPeriod
Indicates the usual or standard time period during which something begins or is initiated.
-
D.
releasedDuring
Indicates that one entity was released within the time period defined by another entity.
-
E.
consoleReleaseDate
Indicates the calendar date on which a particular game console was first released to the public.
- F. None of above. chosen
Provenance (4 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_69c008f9955881909bfa8348b56b4739 |
completed | March 22, 2026, 3:21 p.m. |
| NER | Named-entity recognition | batch_69c01f9b59bc8190a8758b3be54831e9 |
completed | March 22, 2026, 4:58 p.m. |
| PD | Predicate disambiguation | batch_69c01b0c50e48190a1b03ecd20ca440b |
completed | March 22, 2026, 4:38 p.m. |
| PDg | Predicate description generation | batch_69c01f4032408190a4f0d2eb21ebd870 |
completed | March 22, 2026, 4:56 p.m. |
Created at: March 22, 2026, 3:34 p.m.