Triple
T21643345
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Plum Pie |
E534150
|
entity |
| Predicate | hasRecurringElements |
P10543
|
FINISHED |
| Object | running gags |
—
|
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: running gags | Statement: [Plum Pie, hasRecurringElements, running gags]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasRecurringElements Context triple: [Plum Pie, hasRecurringElements, running gags]
-
A.
hasRecurringElement
chosen
Indicates that an entity includes an element that appears repeatedly or occurs multiple times within it.
-
B.
hasRecurringActor
Indicates that an actor appears repeatedly across multiple instances or episodes within a work or series.
-
C.
hasRepetition
Indicates that something occurs, appears, or is performed more than once, showing recurrence or repeated instances within a given context.
-
D.
hasRecurringRole
Indicates that an entity repeatedly appears or participates in a role within an ongoing or multiple related contexts over time.
-
E.
hasRecurringSpecial
Indicates that an entity regularly offers or features a special deal, item, or promotion that recurs over time.
- 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_69e0c466aec88190ba39c7543dbc8ba2 |
completed | April 16, 2026, 11:13 a.m. |
| NER | Named-entity recognition | batch_69ef53930644819086b0f499e1b8ae63 |
completed | April 27, 2026, 12:16 p.m. |
| PD | Predicate disambiguation | batch_69e69677b9c48190bf81f795aa8ad74e |
completed | April 20, 2026, 9:11 p.m. |
Created at: April 16, 2026, 6:35 p.m.