Triple
T972008
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Life in Cold Blood |
E20964
|
entity |
| Predicate | originalRelease |
P22704
|
FINISHED |
| Object | 2008 |
—
|
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: 2008 | Statement: [Life in Cold Blood, originalRelease, 2008]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: originalRelease Context triple: [Life in Cold Blood, originalRelease, 2008]
-
A.
firstReleasedAs
Indicates the original title or form under which an entity (such as a work, product, or version) was initially released before any later re-releases, renamings, or editions.
-
B.
initialReleaseWith
Indicates that two or more entities were first released together as part of the same initial release event or package.
-
C.
originalText
Indicates that one text is the initial, unmodified version from which other versions, translations, or representations are derived.
-
D.
publicRelease
Indicates that something is made available to the general public, typically after any private or restricted access period has ended.
-
E.
originallyIn
Indicates that something first appeared, was created, or was initially located within a particular context, source, or place.
- 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_69a493b33d2c81909c52c369d3ca8436 |
completed | March 1, 2026, 7:29 p.m. |
| NER | Named-entity recognition | batch_69a4b44c38f08190997e141d424e9e04 |
completed | March 1, 2026, 9:49 p.m. |
| PD | Predicate disambiguation | batch_69a4b2a6aa2c8190aebba71320ab678f |
completed | March 1, 2026, 9:41 p.m. |
| PDg | Predicate description generation | batch_69a4b38630848190bd3898a4f42018ad |
completed | March 1, 2026, 9:45 p.m. |
Created at: March 1, 2026, 7:40 p.m.