Triple
T22484012
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Sunshine Daydream |
E555835
|
entity |
| Predicate | commonlyFollows |
P111905
|
FINISHED |
| Object | Sugar Magnolia main song section |
—
|
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: Sugar Magnolia main song section | Statement: [Sunshine Daydream, commonlyFollows, Sugar Magnolia main song section]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: commonlyFollows Context triple: [Sunshine Daydream, commonlyFollows, Sugar Magnolia main song section]
-
A.
commonlyLinkedTo
chosen
Indicates that one entity is frequently or typically associated, connected, or co-occurring with another entity.
-
B.
followsBy
Indicates that one event, state, or entity occurs or comes immediately after another in a sequence or order.
-
C.
followedIn
Indicates that one entity began following or subscribing to another entity, typically in a social or sequential context.
-
D.
followsTo
Indicates that one entity moves or proceeds behind another entity toward a specific destination or target.
-
E.
followsDisc
Indicates that one entity comes after another in a sequence or order, typically in a discrete or stepwise progression.
- 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_69e11e53897c819088863779f8c50bb0 |
completed | April 16, 2026, 5:37 p.m. |
| NER | Named-entity recognition | batch_69f15c3b03d881909e286a124c1a2b1c |
completed | April 29, 2026, 1:17 a.m. |
| PD | Predicate disambiguation | batch_69e898b6eee08190ba673a0ee329e671 |
completed | April 22, 2026, 9:45 a.m. |
Created at: April 16, 2026, 8:49 p.m.