Triple
T3087364
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Ribbon in the Sky |
E64403
|
entity |
| Predicate | isCelebratedFor |
P22
|
FINISHED |
| Object | soulful melody |
—
|
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: soulful melody | Statement: [Ribbon in the Sky, isCelebratedFor, soulful melody]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isCelebratedFor Context triple: [Ribbon in the Sky, isCelebratedFor, soulful melody]
-
A.
notableFor
chosen
Indicates that an entity is especially recognized or distinguished for a particular quality, achievement, characteristic, or role.
-
B.
isCelebratedWith
Indicates that an event, occasion, or person is marked or honored using a particular method, activity, or accompanying element (e.g., a party, ritual, or object).
-
C.
famousForEvent
Indicates that an entity is widely known or recognized specifically because of a particular event.
-
D.
formerlyKnownFor
Indicates that an entity was previously recognized or notable for a particular role, attribute, or activity, but is no longer primarily associated with it.
-
E.
notableAwardedFor
Indicates that an award is notable specifically for being given in recognition of a particular work, achievement, or contribution.
- 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_69ad857c97d88190b26f9b1c90839c77 |
completed | March 8, 2026, 2:19 p.m. |
| NER | Named-entity recognition | batch_69ada209fd24819088d887de0a4158f4 |
completed | March 8, 2026, 4:21 p.m. |
| PD | Predicate disambiguation | batch_69ad9ded78f881908be6fc0fb7c35764 |
completed | March 8, 2026, 4:03 p.m. |
Created at: March 8, 2026, 3:03 p.m.