Triple
T34629709
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | The Royal Family |
E889239
|
entity |
| Predicate | productionDisruptedBy |
P44223
|
FINISHED |
| Object | death of Redd Foxx |
—
|
LITERAL 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: death of Redd Foxx | Statement: [The Royal Family, productionDisruptedBy, death of Redd Foxx]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: productionDisruptedBy Context triple: [The Royal Family, productionDisruptedBy, death of Redd Foxx]
-
A.
troubledProduction
chosen
Indicates that the production process of a work (such as a film, show, or project) experienced significant difficulties, delays, or conflicts.
-
B.
disruptedIn
Indicates that a normal process, function, or state is interrupted, impaired, or thrown into disorder within the specified context.
-
C.
productionResumption
Indicates the restarting or continuation of production activities after a pause or interruption.
-
D.
constructionCaused
Indicates that one construction activity, process, or project is the cause of another event, condition, or outcome.
-
E.
causedGasSupplyDisruption
Indicates that one entity was responsible for interrupting or disturbing the supply of gas to another entity or area.
- 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_69f349d64a388190a013cfa9bd33fad7 |
completed | April 30, 2026, 12:23 p.m. |
| NER | Named-entity recognition | batch_69feaa483fcc81909d8a46b38a8717bf |
completed | May 9, 2026, 3:30 a.m. |
| PD | Predicate disambiguation | batch_69fea8c9d45c81908ccc8619e5fefac1 |
completed | May 9, 2026, 3:23 a.m. |
Created at: May 1, 2026, 2:04 a.m.