Triple
T15275529
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Josh Kramon |
E365127
|
entity |
| Predicate | notableSeriesStatus |
P117915
|
FINISHED |
| Object | cult television series |
—
|
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: cult television series | Statement: [Josh Kramon, notableSeriesStatus, cult television series]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: notableSeriesStatus Context triple: [Josh Kramon, notableSeriesStatus, cult television series]
-
A.
notableSeriesRun
Indicates that an entity is recognized for having a significant or distinguished run within a particular series or sequence of events.
-
B.
seriesStatus
Indicates the current state or phase of a series within its lifecycle (e.g., ongoing, completed, canceled, or planned).
-
C.
statusInTVSeries
Indicates the role or standing an entity holds within a particular TV series, such as main, recurring, or guest status.
-
D.
notableSeries
Indicates that an entity is a significant or well-known installment within a particular series or franchise.
-
E.
notableOriginalSeries
Indicates that an entity is recognized as a significant or distinguished original series associated with another entity (such as a platform, creator, or franchise).
- 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_69d85a0f08408190b3c3259ae35d79d2 |
completed | April 10, 2026, 2:01 a.m. |
| NER | Named-entity recognition | batch_69e00952731c8190bf6a5e6e10c95b94 |
completed | April 15, 2026, 9:55 p.m. |
| PD | Predicate disambiguation | batch_69deca90739081909bd1b797cdb8af2b |
completed | April 14, 2026, 11:15 p.m. |
| PDg | Predicate description generation | batch_69decf2ca6148190967c319728ec3661 |
completed | April 14, 2026, 11:35 p.m. |
Created at: April 10, 2026, 3:14 a.m.