Triple
T32490279
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Rolling Papers 2 |
E830364
|
entity |
| Predicate | breakthroughPredecessor |
P129692
|
FINISHED |
| Object | Rolling Papers |
—
|
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: Rolling Papers | Statement: [Rolling Papers 2, breakthroughPredecessor, Rolling Papers]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: breakthroughPredecessor Context triple: [Rolling Papers 2, breakthroughPredecessor, Rolling Papers]
-
A.
hasBreakthroughPredecessor
chosen
Indicates that one entity is recognized as a significant, precedent-setting breakthrough that directly precedes and enables another entity.
-
B.
breakthroughBy
Indicates that a significant discovery, innovation, or advance was achieved or brought about by a particular agent or entity.
-
C.
breakthrough
Indicates a significant and often sudden advance or discovery that overcomes a major obstacle in a process, field, or endeavor.
-
D.
markedBreakthroughOf
Indicates that an event, action, or development signified a major breakthrough or turning point for something.
-
E.
eraOfBreakthrough
Indicates the time period during which a significant breakthrough or major advancement occurred.
- 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_69f34920aa4081908d8fb0277414b911 |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_69f6c4070c808190b633acf2a95b4e56 |
completed | May 3, 2026, 3:41 a.m. |
| PD | Predicate disambiguation | batch_69f6bd25bed08190befcabd3a41ffadf |
completed | May 3, 2026, 3:12 a.m. |
Created at: May 1, 2026, 12:59 a.m.