Triple
T33183344
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Karl Hettinger |
E849394
|
entity |
| Predicate | genreOfNotableEvent |
P119424
|
FINISHED |
| Object | true crime |
—
|
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 crime | Statement: [Karl Hettinger, genreOfNotableEvent, true crime]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: genreOfNotableEvent Context triple: [Karl Hettinger, genreOfNotableEvent, true crime]
-
A.
genreOfDescribedEvents
chosen
Indicates that one entity specifies the genre or type category of the events described by another entity.
-
B.
notableCategoryType
Indicates that an entity is notably associated with or classified under a particular category type.
-
C.
notableEventMentionedIn
Indicates that a particular notable event is referenced or discussed within a specified source or document.
-
D.
notableCategory
Indicates that an entity is recognized as notable or significant within a particular category or classification.
-
E.
notableEventIncluded
Indicates that a particular notable event is contained within, or forms part of, a larger collection, record, or context.
- 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_69f3495d06508190b0b7729982982cea |
completed | April 30, 2026, 12:21 p.m. |
| NER | Named-entity recognition | batch_69f7465687bc8190a9da44d62b634ed7 |
completed | May 3, 2026, 12:57 p.m. |
| PD | Predicate disambiguation | batch_69f743f4ceb08190a21fe7f4a99b166b |
completed | May 3, 2026, 12:47 p.m. |
Created at: May 1, 2026, 1:29 a.m.