Triple
T37677795
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Osbourne family |
E938142
|
entity |
| Predicate | hasSpinOffShow |
P7226
|
FINISHED |
| Object | Osbournes Reloaded |
—
|
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: Osbournes Reloaded | Statement: [Osbourne family, hasSpinOffShow, Osbournes Reloaded]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasSpinOffShow Context triple: [Osbourne family, hasSpinOffShow, Osbournes Reloaded]
-
A.
hasSpinOff
chosen
Indicates that one entity is a derivative or spin-off product, work, or organization that originated from another entity.
-
B.
hasSpinOffLabel
Indicates that one entity serves as a spin-off label or subsidiary label that originated from another label entity.
-
C.
hasSpinOffDevelopment
Indicates that one entity has led to or produced a derivative or spin-off development based on it.
-
D.
hasSpinOffPlatform
Indicates that one entity has given rise to or is associated with a derivative or spin-off platform based on the original.
-
E.
hasSpinOffPublisher
Indicates that an entity has another publisher that was created as a spin-off derived from it.
- 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_69f76ed7b1408190ba8c93c53cb8becf |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_69ff0214d7348190904688376df99bce |
completed | May 9, 2026, 9:44 a.m. |
| PD | Predicate disambiguation | batch_69feffd62fec8190a855922c8b3c57cf |
completed | May 9, 2026, 9:35 a.m. |
Created at: May 3, 2026, 4:18 p.m.