Triple
T20955750
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Krik? Krak! |
E516095
|
entity |
| Predicate | isInterrelatedCycleOfStories |
P40707
|
FINISHED |
| Object | true |
—
|
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 | Statement: [Krik? Krak!, isInterrelatedCycleOfStories, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isInterrelatedCycleOfStories Context triple: [Krik? Krak!, isInterrelatedCycleOfStories, true]
-
A.
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.
-
B.
associatedTale
Indicates that one entity is linked or connected to a particular tale, story, or narrative.
-
C.
hasSiblingInStory
Indicates that one character in a narrative has at least one sibling who also appears within the same story.
-
D.
narrativeConnection
Indicates a meaningful relationship between elements within a narrative, such as events, characters, or scenes, that links them in terms of plot, causality, or thematic continuity.
-
E.
isNarrativelyGroupedWith
Indicates that two or more elements are treated as part of the same narrative unit, sequence, or storyline within a larger 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_69e0b4fcd678819087a304291f14330a |
completed | April 16, 2026, 10:07 a.m. |
| NER | Named-entity recognition | batch_69e6fb6b19048190b266ed24f6fc1a97 |
completed | April 21, 2026, 4:22 a.m. |
| PD | Predicate disambiguation | batch_69e5c9b1bae48190a845165fed1b005e |
completed | April 20, 2026, 6:37 a.m. |
Created at: April 16, 2026, 1:28 p.m.