Triple
T35277038
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | So Much (for) Stardust |
E1018826
|
entity |
| Predicate | returnToLabel |
P191043
|
FINISHED |
| Object | Fueled by Ramen |
—
|
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: Fueled by Ramen | Statement: [So Much (for) Stardust, returnToLabel, Fueled by Ramen]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: returnToLabel Context triple: [So Much (for) Stardust, returnToLabel, Fueled by Ramen]
-
A.
returnedToLocation
Indicates that an entity has gone back to a specific location it was previously at.
-
B.
reentryLocation
Indicates the place or area where an entity returns or re-enters after having left or exited a previous location or state.
-
C.
marksReturnTo
Indicates a point, event, or condition that signifies the resumption or coming back of something or someone to a prior state, place, or activity.
-
D.
returnRoute
Indicates that an entity serves as the route used to return from a destination back to an origin or starting point.
-
E.
returnToStage
Indicates that an entity goes back onto a stage or performance area after having left it.
- 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_69f76de5c4788190896ad598ae7d6bc6 |
completed | May 3, 2026, 3:46 p.m. |
| NER | Named-entity recognition | batch_69fcd867f36081908c88c55a6a1404c1 |
completed | May 7, 2026, 6:22 p.m. |
| PD | Predicate disambiguation | batch_69fcd1f47b188190b4cf4b4c748d9d03 |
completed | May 7, 2026, 5:55 p.m. |
| PDg | Predicate description generation | batch_69fcd866dd248190bff61c43bee93f54 |
completed | May 7, 2026, 6:22 p.m. |
Created at: May 3, 2026, 4:02 p.m.