Triple
T23826903
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Love on the Weekend |
E589400
|
entity |
| Predicate | isLeadSingleOf |
P102128
|
FINISHED |
| Object | The Search for Everything |
—
|
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: The Search for Everything | Statement: [Love on the Weekend, isLeadSingleOf, The Search for Everything]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isLeadSingleOf Context triple: [Love on the Weekend, isLeadSingleOf, The Search for Everything]
-
A.
isEnergeticLeadSingleFrom
Indicates that something serves as the primary, high-energy lead single originating from a particular source, such as an album or artist.
-
B.
isSingle
Indicates that an entity is not currently in a romantic relationship or legally married.
-
C.
isLeadTrackOf
chosen
Indicates that a track serves as the primary or featured track associated with a particular release, album, or recording project.
-
D.
coLeadOf
Indicates a relationship where two or more entities share joint leadership responsibility over the same project, group, or initiative.
-
E.
leadSingle
Indicates that an entity serves as the primary or featured performer, contributor, or focus in a single work or instance.
- 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_69e25d1922d481909cab567c06a802ab |
completed | April 17, 2026, 4:17 p.m. |
| NER | Named-entity recognition | batch_69f1c7f23ed08190bc2b86ccb2b81611 |
completed | April 29, 2026, 8:57 a.m. |
| PD | Predicate disambiguation | batch_69f156036ad48190bc2ffdaf39218bcb |
completed | April 29, 2026, 12:51 a.m. |
Created at: April 17, 2026, 8 p.m.