Triple
T33364667
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Stairsteps – 2nd Resurrection |
E854316
|
entity |
| Predicate | precedesReunionOrLaterWorkBy |
P103306
|
FINISHED |
| Object | Five Stairsteps |
—
|
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: Five Stairsteps | Statement: [Stairsteps – 2nd Resurrection, precedesReunionOrLaterWorkBy, Five Stairsteps]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: precedesReunionOrLaterWorkBy Context triple: [Stairsteps – 2nd Resurrection, precedesReunionOrLaterWorkBy, Five Stairsteps]
-
A.
hasReunion
Indicates that a reunion event or gathering occurs between the related entities.
-
B.
precedesInCareer
Indicates that one entity’s role, position, or stage in a professional path occurs earlier in time than another entity’s corresponding role, position, or stage in that same career trajectory.
-
C.
precedesWorkBySameCreator
chosen
Indicates that one work comes before another work created by the same creator in a sequence or chronology.
-
D.
previousWorkAfterHiatusOf
Indicates that one work directly follows and resumes activity after a hiatus or break from a previous work.
-
E.
previouslyIn
Indicates that an entity was located in, part of, or associated with another entity at some earlier time, but is not necessarily so now.
- 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_69f3496bda8c8190bfc8fade9d1b791c |
completed | April 30, 2026, 12:22 p.m. |
| NER | Named-entity recognition | batch_69fcf36d2894819089b7db8e91b63c9d |
completed | May 7, 2026, 8:17 p.m. |
| PD | Predicate disambiguation | batch_69fcf25c0a108190bfa823474098640b |
completed | May 7, 2026, 8:13 p.m. |
Created at: May 1, 2026, 1:34 a.m.