Triple
T382024
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Pride and Prejudice (1995 TV series) |
E8700
|
entity |
| Predicate | homeMediaRelease |
P10682
|
FINISHED |
| Object | VHS |
—
|
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: VHS | Statement: [Pride and Prejudice (1995 TV series), homeMediaRelease, VHS]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: homeMediaRelease Context triple: [Pride and Prejudice (1995 TV series), homeMediaRelease, VHS]
-
A.
mediaCoverage
Indicates that one entity reports on, documents, or broadcasts information about another entity through news or media channels.
-
B.
announcedThat
Indicates that one entity publicly communicated or declared a specific fact, decision, or piece of information about another entity or situation.
-
C.
releaseOf
Indicates the act or event of something being set free, made available, or discharged from a prior state of containment, control, or restriction.
-
D.
mediaAccess
Indicates that one entity has the ability, permission, or means to view, use, or interact with a particular media resource.
-
E.
primaryMedium
Indicates the main material, format, or channel through which something is created, expressed, or communicated.
- 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_69a2e7f47dd08190a4e294ccbbe46cd4 |
completed | Feb. 28, 2026, 1:04 p.m. |
| NER | Named-entity recognition | batch_69a2ec2e3d5c8190b358bd9fd6b16a14 |
completed | Feb. 28, 2026, 1:22 p.m. |
| PD | Predicate disambiguation | batch_69a2e96602188190b0cbc167f55a9237 |
completed | Feb. 28, 2026, 1:11 p.m. |
| PDg | Predicate description generation | batch_69a2ea2dc3088190a2aeb4496aff3582 |
completed | Feb. 28, 2026, 1:14 p.m. |
Created at: Feb. 28, 2026, 1:08 p.m.