Triple
T36085047
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | "Cash Me Ousside, How Bout Dat" |
E1043752
|
entity |
| Predicate | originatedOn |
P86814
|
FINISHED |
| Object | Dr. Phil |
E480138
|
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: Dr. Phil | Statement: ["Cash Me Ousside, How Bout Dat", originatedOn, Dr. Phil]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: originatedOn Context triple: ["Cash Me Ousside, How Bout Dat", originatedOn, Dr. Phil]
-
A.
originatesAs
Indicates that one entity begins, arises, or comes into existence in the form, state, or role specified by another entity.
-
B.
originallyHostedAt
chosen
Indicates the location or venue where something was first hosted or took place before any subsequent moves or changes.
-
C.
originatedAround
Indicates that something began, emerged, or came into existence approximately at a specified time or within a loosely defined period.
-
D.
createdAtLocation
Indicates the place or location where an entity was originally created or brought into existence.
-
E.
originallyBy
Indicates that one entity is the original creator, author, or source of another entity.
- 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_6a38d5428d64819099ebe4842364c767 |
completed | June 22, 2026, 6:25 a.m. |
| PD | Predicate disambiguation | batch_6a037a0895b48190acdd88dc10db7be7 |
completed | May 12, 2026, 7:05 p.m. |
Created at: May 3, 2026, 4:08 p.m.