Triple
T25279607
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Aimee Osbourne |
E633790
|
entity |
| Predicate | refusedToAppearIn |
P158329
|
FINISHED |
| Object | The Osbournes |
—
|
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: The Osbournes | Statement: [Aimee Osbourne, refusedToAppearIn, The Osbournes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: refusedToAppearIn Context triple: [Aimee Osbourne, refusedToAppearIn, The Osbournes]
-
A.
refusedToExplain
Indicates that an entity declined or failed to provide an explanation about something to another entity or audience.
-
B.
refusedToAbdicate
Indicates that a person who holds power or authority declined to give up or renounce their position when expected or requested to do so.
-
C.
appearsInCourt
Indicates that an entity is formally present and participating in a legal proceeding before a court.
-
D.
refusesToLeave
Indicates that an entity is unwilling to depart from a place, situation, or state despite expectation or pressure to do so.
-
E.
refused to play for
Indicates that one party declined or rejected participating or performing on behalf of another party, typically in a team, organization, or representative role.
- F. None of above. chosen
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_69e75a9402fc81909362ca85277c06d9 |
completed | April 21, 2026, 11:08 a.m. |
| NER | Named-entity recognition | batch_69f48e02a94c819090718463605abfb5 |
completed | May 1, 2026, 11:26 a.m. |
| PD | Predicate disambiguation | batch_69f45d06d0388190b36ecde92013624a |
completed | May 1, 2026, 7:57 a.m. |
| PDg | Predicate description generation | batch_69f465699c9c8190ac7b4b32b782550c |
completed | May 1, 2026, 8:33 a.m. |
Created at: April 21, 2026, 1:18 p.m.