Triple
T35261877
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Star Trek: The Original Series Season 2 DVD |
E1018389
|
entity |
| Predicate | containsBonusContent |
P147622
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [Star Trek: The Original Series Season 2 DVD, containsBonusContent, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: containsBonusContent Context triple: [Star Trek: The Original Series Season 2 DVD, containsBonusContent, true]
-
A.
hasDeluxeContent
Indicates that an entity includes or is associated with enhanced or premium content beyond the standard offering.
-
B.
hasBonusTrackStatus
Indicates whether an item (such as a track or release) is designated as a bonus track in relation to a primary work or edition.
-
C.
hasBonusMaterial
chosen
Indicates that an item includes additional supplementary content beyond its main or primary material.
-
D.
hasCompanionContent
Indicates that one piece of content is accompanied by related or supplementary content intended to be used or consumed together.
-
E.
hasGameContent
Indicates that an entity includes, provides, or is associated with game-related material or features.
- 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_69f76de4be5c8190a51705c07612cac8 |
completed | May 3, 2026, 3:46 p.m. |
| NER | Named-entity recognition | batch_6a00b6e163308190adeb1d6eb8558641 |
completed | May 10, 2026, 4:48 p.m. |
| PD | Predicate disambiguation | batch_6a00b67e0e388190b08ad66cee4cb0d7 |
completed | May 10, 2026, 4:46 p.m. |
Created at: May 3, 2026, 4:02 p.m.