Triple
T15354943
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | The Gang |
E367146
|
entity |
| Predicate | recurringStoryElement |
P40707
|
FINISHED |
| Object | elaborate scams |
—
|
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: elaborate scams | Statement: [The Gang, recurringStoryElement, elaborate scams]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: recurringStoryElement Context triple: [The Gang, recurringStoryElement, elaborate scams]
-
A.
storyElement
Indicates that one entity functions as a narrative component or part within the structure of another entity’s story.
-
B.
retellsStoryOf
Indicates that one entity recounts or narrates the story originally told or experienced by another entity.
-
C.
narrativeCycle
chosen
Indicates a recurring or structured sequence of narrative events or themes that repeat or progress in a cyclical pattern within a story or across stories.
-
D.
hasRecurringProtagonists
Indicates that the same main character or set of main characters appears repeatedly across multiple works or installments in a series.
-
E.
storyBy
Indicates that one entity is the creator or author of the story associated with another entity.
- 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_69d85a1355608190a6673ddb67231d54 |
completed | April 10, 2026, 2:01 a.m. |
| NER | Named-entity recognition | batch_69e03e2c00648190ae2325e1ee58dcfd |
completed | April 16, 2026, 1:41 a.m. |
| PD | Predicate disambiguation | batch_69deca991e5081908b0df3d1ee7d5338 |
completed | April 14, 2026, 11:15 p.m. |
Created at: April 10, 2026, 3:18 a.m.