Triple
T37057963
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Sleepy Brown |
E917244
|
entity |
| Predicate | collaboratedOnSingleWith |
P107310
|
FINISHED |
| Object | So Fresh, So Clean – OutKast |
—
|
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: So Fresh, So Clean – OutKast | Statement: [Sleepy Brown, collaboratedOnSingleWith, So Fresh, So Clean – OutKast]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: collaboratedOnSingleWith Context triple: [Sleepy Brown, collaboratedOnSingleWith, So Fresh, So Clean – OutKast]
-
A.
hasCollaboratedIn
Indicates that two or more entities have worked together on a shared project, task, or activity.
-
B.
frequentlyCollaboratedWith
Indicates that two entities have worked together on shared activities or projects on a recurring or regular basis.
-
C.
collaboratedWithInKeyWork
chosen
Indicates that two or more entities worked together in creating or contributing to a specific, significant work or project.
-
D.
collaborationOf
Indicates a relationship in which two or more entities work together jointly toward a shared goal or outcome.
-
E.
publishedInCollaborationWith
Indicates that an entity was published as a result of a joint effort or partnership 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_69f76e95fa40819091e14681087ae5e4 |
completed | May 3, 2026, 3:49 p.m. |
| NER | Named-entity recognition | batch_69fba2877b248190a974eb092243c0c4 |
completed | May 6, 2026, 8:20 p.m. |
| PD | Predicate disambiguation | batch_69fb8d06a1b48190a937aa410d159dfa |
completed | May 6, 2026, 6:48 p.m. |
Created at: May 3, 2026, 4:14 p.m.