Triple
T34629715
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | The Royal Family |
E889239
|
entity |
| Predicate | featuredComedian |
P185309
|
FINISHED |
| Object | Redd Foxx |
E51050
|
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: Redd Foxx | Statement: [The Royal Family, featuredComedian, Redd Foxx]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: featuredComedian Context triple: [The Royal Family, featuredComedian, Redd Foxx]
-
A.
comedian
Indicates that the subject performs comedy or is recognized for engaging in comedic entertainment.
-
B.
starsComedianKnownFor
Indicates that a work features a comedian who is particularly recognized or famous for that role or performance.
-
C.
hasLeadComedian
chosen
Indicates that one entity serves as the primary or main comedian associated with another entity, such as a show, event, or performance.
-
D.
isEntertainer
Indicates that one entity works in entertainment, performing or creating content to amuse or engage an audience.
-
E.
comedicDynamicWith
Indicates a relationship in which two or more entities interact in a way that creates or supports comedic effect, timing, or contrast.
- 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_69f349d64a388190a013cfa9bd33fad7 |
completed | April 30, 2026, 12:23 p.m. |
| NER | Named-entity recognition | batch_6a0352b6c7dc81908f190060eb1e1857 |
completed | May 12, 2026, 4:17 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a3779319c108190865578b13c061bfd |
completed | June 21, 2026, 5:40 a.m. |
| PD | Predicate disambiguation | batch_6a03507c37d4819091068b2ec5cacef9 |
completed | May 12, 2026, 4:08 p.m. |
Created at: May 1, 2026, 2:04 a.m.