Triple
T26355708
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Playa |
E663044
|
entity |
| Predicate | songwriterForOthers |
P157915
|
FINISHED |
| Object | Static Major wrote for Ginuwine |
—
|
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: Static Major wrote for Ginuwine | Statement: [Playa, songwriterForOthers, Static Major wrote for Ginuwine]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: songwriterForOthers Context triple: [Playa, songwriterForOthers, Static Major wrote for Ginuwine]
-
A.
songwritingForOthers
chosen
Indicates that an entity creates songs intended to be performed or used by other entities rather than themselves.
-
B.
songwriterCollective
Indicates a relationship where a songwriter is a member of, or affiliated with, a collective group of songwriters.
-
C.
coSongwriter
Indicates that two or more entities collaborated in writing the same song.
-
D.
songwritingCredit
Indicates that one entity is credited as a songwriter or co-songwriter for a musical work associated with another entity.
-
E.
songwriterOn
Indicates that one entity serves as the songwriter or composer responsible for creating the musical content associated with another entity.
- 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_69ee8130fc44819094e5ab1da201cd7b |
completed | April 26, 2026, 9:18 p.m. |
| NER | Named-entity recognition | batch_69f60feed66c8190a24ee1364881733e |
completed | May 2, 2026, 2:53 p.m. |
| PD | Predicate disambiguation | batch_69f602d2ec748190ae95154f34c7878f |
completed | May 2, 2026, 1:57 p.m. |
Created at: April 26, 2026, 10:48 p.m.