Triple
T33364652
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Stairsteps – 2nd Resurrection |
E854316
|
entity |
| Predicate | marksRebrandingAs |
P157594
|
FINISHED |
| Object | The 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: The Stairsteps | Statement: [Stairsteps – 2nd Resurrection, marksRebrandingAs, The Stairsteps]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: marksRebrandingAs Context triple: [Stairsteps – 2nd Resurrection, marksRebrandingAs, The Stairsteps]
-
A.
marksStatus
Indicates that one entity assigns, records, or updates the status or condition of another entity.
-
B.
marksOn
Indicates that one entity bears visible signs, traces, or imprints that have been made or left by another entity.
-
C.
brandingReplaced
chosen
Indicates that one branding has been superseded or substituted by another branding.
-
D.
registrationMark
Indicates that an entity bears a specific official registration identifier or code assigned by an authority.
-
E.
brandingStatus
Indicates the current state or condition of an entity’s branding, such as whether its brand identity has been defined, applied, updated, or is pending.
- 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_69f6e3156ea48190b604e414665ef351 |
completed | May 3, 2026, 5:54 a.m. |
| PD | Predicate disambiguation | batch_69f6de0b9ba48190887c9eb5d06a2e94 |
completed | May 3, 2026, 5:32 a.m. |
Created at: May 1, 2026, 1:34 a.m.