Triple
T31352135
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Fat Bitch |
E799624
|
entity |
| Predicate | creditedPerformerUniverse |
P58964
|
FINISHED |
| Object | Tracy Jordan |
—
|
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: Tracy Jordan | Statement: [Fat Bitch, creditedPerformerUniverse, Tracy Jordan]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: creditedPerformerUniverse Context triple: [Fat Bitch, creditedPerformerUniverse, Tracy Jordan]
-
A.
hasPerformerCredit
Indicates that a performer is credited for their role or contribution in a specific work, event, or production.
-
B.
creditedIn
Indicates that an entity is acknowledged or listed as a contributor or source within a particular work, record, or context.
-
C.
hasInUniverseRole
chosen
Indicates that an entity holds or performs a specific role or function within a particular fictional or defined universe.
-
D.
associatedPerformerPersona
Indicates a relationship where a performer is linked to a specific persona or role identity they adopt in their performances.
-
E.
performerCreditedAs
Indicates that a performer is associated with a work under a specific credited name or alias.
- 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_69f224e5e9bc8190a16339328897c4f8 |
completed | April 29, 2026, 3:33 p.m. |
| NER | Named-entity recognition | batch_69f6a0ea04888190ac3a813b603bcb5c |
completed | May 3, 2026, 1:12 a.m. |
| PD | Predicate disambiguation | batch_69f69fe463248190aa78128abeab1183 |
completed | May 3, 2026, 1:07 a.m. |
Created at: April 29, 2026, 9:17 p.m.