Triple
T36085146
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | These Heaux |
E1043754
|
entity |
| Predicate | basedOnInternetPersonaOf |
P155184
|
FINISHED |
| Object | Bhad Bhabie |
—
|
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: Bhad Bhabie | Statement: [These Heaux, basedOnInternetPersonaOf, Bhad Bhabie]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: basedOnInternetPersonaOf Context triple: [These Heaux, basedOnInternetPersonaOf, Bhad Bhabie]
-
A.
basedOnPersona
chosen
Indicates that something is created, customized, or decided according to a specific persona’s characteristics, preferences, or profile.
-
B.
ultimatePersona
Indicates that one entity represents the final, most complete, or most authoritative persona or identity of another entity.
-
C.
basedOnRealPersonFor
Indicates that one entity is created, modeled, or inspired using a specific real person as its basis.
-
D.
primaryRoleOnLine
Indicates that an entity serves as the main or most important role associated with a particular line (such as a transit line, product line, or communication line).
-
E.
hasPersona
Indicates that an entity possesses or is associated with a particular persona, role, or character profile.
- 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_69f76e3154908190a6f702671c2bea08 |
completed | May 3, 2026, 3:48 p.m. |
| NER | Named-entity recognition | batch_69ff3e1762d8819089a60e402e682817 |
completed | May 9, 2026, 2 p.m. |
| PD | Predicate disambiguation | batch_69ff3d8c6f308190a0646b1432752eb8 |
completed | May 9, 2026, 1:58 p.m. |
Created at: May 3, 2026, 4:08 p.m.