Triple
T33610935
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Purple Hearts |
E860983
|
entity |
| Predicate | hasSungHook |
P70265
|
FINISHED |
| Object | Summer Walker |
—
|
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: Summer Walker | Statement: [Purple Hearts, hasSungHook, Summer Walker]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasSungHook Context triple: [Purple Hearts, hasSungHook, Summer Walker]
-
A.
hasSung
Indicates that an entity has performed the action of singing at least once.
-
B.
hasHookSinger
chosen
Indicates that one entity serves as the hook singer (performing the main recurring vocal refrain) for another entity, typically a song or musical track.
-
C.
hasSungChorus
Indicates that an entity has performed or participated in singing the chorus section of a song.
-
D.
hasChorusHook
Indicates that a musical work features a prominent, recurring chorus section that serves as a memorable hook.
-
E.
hasSong
Indicates that one entity possesses, features, or includes a particular song.
- 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_69f3498037c88190a4500f002b5540e0 |
completed | April 30, 2026, 12:22 p.m. |
| NER | Named-entity recognition | batch_69ff6074bcd4819090b72cd6209ff206 |
completed | May 9, 2026, 4:27 p.m. |
| PD | Predicate disambiguation | batch_69ff600aba888190812a6e7eca0283b8 |
completed | May 9, 2026, 4:25 p.m. |
Created at: May 1, 2026, 1:41 a.m.