Triple
T31853645
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Rage of Angels |
E813129
|
entity |
| Predicate | sequelFormat |
P75239
|
FINISHED |
| Object | television miniseries |
—
|
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: television miniseries | Statement: [Rage of Angels, sequelFormat, television miniseries]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: sequelFormat Context triple: [Rage of Angels, sequelFormat, television miniseries]
-
A.
sequelPlatform
Indicates that one platform is a follow-up or successor to another platform in a series or progression.
-
B.
sequelDirected
Indicates that one work is a sequel to another and was directed by the same director or a specific director associated with that sequel relationship.
-
C.
hasSequelType
chosen
Indicates that one work has a sequel of a specified type or category in relation to another work.
-
D.
sequelStatus
Indicates that one work follows another in a series, continuing its story, chronology, or thematic development as a sequel.
-
E.
hasSequelDepiction
Indicates that one depiction of something is followed by another depiction that continues its story or sequence.
- 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_69f348ebf32881908d9439646933dc76 |
completed | April 30, 2026, 12:19 p.m. |
| NER | Named-entity recognition | batch_69f6b03f3b148190a1b096da2a6c5864 |
completed | May 3, 2026, 2:17 a.m. |
| PD | Predicate disambiguation | batch_69f6aca59d4881908d14ed47962703bd |
completed | May 3, 2026, 2:02 a.m. |
Created at: April 30, 2026, 11:52 p.m.