Triple
T38251367
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 21 Up |
E1014057
|
entity |
| Predicate | hasSequelInterval |
P202882
|
FINISHED |
| Object | 7 years |
—
|
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: 7 years | Statement: [21 Up, hasSequelInterval, 7 years]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasSequelInterval Context triple: [21 Up, hasSequelInterval, 7 years]
-
A.
hasSequelLikeCycle
Indicates that a work is part of a sequence where sequels form a cycle, such that following the sequel relationships eventually leads back to the original work.
-
B.
hasSequelType
Indicates that one work has a sequel of a specified type or category in relation to another work.
-
C.
hasSequel
Indicates that one work is followed by another work that continues its story, timeline, or thematic development.
-
D.
hasSequelNumber
Indicates that an entity is followed by another work in a series identified by a specific sequential number.
-
E.
hasSequelPiece
Indicates that one creative work is a subsequent installment or continuation that follows another work in a series.
- F. None of above. chosen
Provenance (4 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_69f76dd7e89c8190b7866bc85aea521b |
completed | May 3, 2026, 3:46 p.m. |
| NER | Named-entity recognition | batch_6a00ca5e907481909d391afd55938a1b |
completed | May 10, 2026, 6:11 p.m. |
| PD | Predicate disambiguation | batch_6a00ca2214348190a674a85ede709e2e |
completed | May 10, 2026, 6:10 p.m. |
| PDg | Predicate description generation | batch_6a00ca5de6748190bc67a1fd9f3d0b3a |
completed | May 10, 2026, 6:11 p.m. |
Created at: May 3, 2026, 4:30 p.m.