Triple
T36085048
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | "Cash Me Ousside, How Bout Dat" |
E1043752
|
entity |
| Predicate | firstSpokenBy |
P2181
|
FINISHED |
| Object | Danielle Bregoli |
E1064081
|
NE 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: Danielle Bregoli | Statement: ["Cash Me Ousside, How Bout Dat", firstSpokenBy, Danielle Bregoli]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: firstSpokenBy Context triple: ["Cash Me Ousside, How Bout Dat", firstSpokenBy, Danielle Bregoli]
-
A.
spokenBy
chosen
Indicates that a particular utterance, statement, or piece of speech is produced or said by a specific entity.
-
B.
currentlySpokenBy
Indicates that a language is presently being used as a spoken language by a person or group.
-
C.
voicedByAlsoKnownFor
Indicates that the person who voices a character is also notably recognized for another specific role or work.
-
D.
protagonistVoicedBy
Indicates that the speaking voice of the main character in a work is provided by a particular performer.
-
E.
introducedByCharacter
Indicates that one character is responsible for presenting, bringing into the story, or otherwise causing another entity to be first revealed or made known.
- F. None of above.
Provenance (4 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_69f76e3154908190a6f702671c2bea08 |
completed | May 3, 2026, 3:48 p.m. |
| NER | Named-entity recognition | batch_6a037c8d06cc8190ab6a5e18d9d2571e |
completed | May 12, 2026, 7:16 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a3d177cf0a08190a99029f1fbb1f485 |
completed | June 25, 2026, 11:56 a.m. |
| PD | Predicate disambiguation | batch_6a037a0895b48190acdd88dc10db7be7 |
completed | May 12, 2026, 7:05 p.m. |
Created at: May 3, 2026, 4:08 p.m.