Triple
T32936499
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Iced |
E842540
|
entity |
| Predicate | hasRecurringSleuth |
—
|
GENERATED |
| Object | Regan Reilly |
—
|
UNRECOGNIZED GENERATED |
How this triple was built (1 step)
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.
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasRecurringSleuth Context triple: [Iced, hasRecurringSleuth, Regan Reilly]
-
A.
recurringSleuth
chosen
Indicates that an entity repeatedly appears in a detective or investigative role within a series of related works or events.
-
B.
hasSleuth
Indicates that an entity is associated with or employs a sleuth (detective) responsible for investigating on its behalf.
-
C.
hasRecurringSpecial
Indicates that an entity regularly offers or features a special deal, item, or promotion that recurs over time.
-
D.
hasRecurringSeriesProtagonists
Indicates that a recurring series features one or more protagonists who appear repeatedly across its installments.
-
E.
hasRecurringActor
Indicates that an actor appears repeatedly across multiple instances or episodes within a work or series.
- F. None of above.
Provenance (1 batch)
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_69f34949727c81909d195c97de3341c8 |
completed | April 30, 2026, 12:21 p.m. |
Created at: May 1, 2026, 1:20 a.m.