Triple
T34969076
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Resolutions |
E1008483
|
entity |
| Predicate | airedInContinuityBetweenEpisodes |
P131935
|
FINISHED |
| Object | "Innocence" |
—
|
NE NERFINISHED |
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: "Innocence" | Statement: [Resolutions, airedInContinuityBetweenEpisodes, "Innocence"]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: airedInContinuityBetweenEpisodes Context triple: [Resolutions, airedInContinuityBetweenEpisodes, "Innocence"]
-
A.
seriesContinuity
Indicates that one work, episode, or installment maintains narrative or canonical continuity with another within the same series.
-
B.
rimContinuity
Indicates that two rim segments are continuous with each other, forming an unbroken boundary or edge.
-
C.
cultContinuity
Indicates the continuation or persistence of a religious cult’s practices, beliefs, or traditions over time.
-
D.
airedWithinSeries
chosen
Indicates that an episode or installment was broadcast as part of, and within the run of, a particular series.
-
E.
titleContinuity
Indicates that two works share a continuous or consistent use of the same title across versions, installments, or related contexts.
- 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_69f76dc78a308190a1ac29ad4a9a4895 |
completed | May 3, 2026, 3:46 p.m. |
| NER | Named-entity recognition | batch_69f78710282c81909146dc0be91e983f |
completed | May 3, 2026, 5:34 p.m. |
| PD | Predicate disambiguation | batch_69f784162134819098413482ef52042f |
completed | May 3, 2026, 5:21 p.m. |
Created at: May 3, 2026, 4 p.m.