Triple
T27938979
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Debbie (Knocked Up) |
E700688
|
entity |
| Predicate | spinOffFocus |
P51499
|
FINISHED |
| Object | central character in This Is 40 |
—
|
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: central character in This Is 40 | Statement: [Debbie (Knocked Up), spinOffFocus, central character in This Is 40]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: spinOffFocus Context triple: [Debbie (Knocked Up), spinOffFocus, central character in This Is 40]
-
A.
spinOff
Indicates that a new entity is created by separating or divesting part of an existing entity, forming an independent offshoot derived from the original.
-
B.
spinOffWork
chosen
Indicates that one work is derived from, based on, or created as a spin-off of another preexisting work.
-
C.
spinoffSetting
Indicates that one work is set in a narrative world or environment derived from, but distinct from, the setting of another work.
-
D.
focusShift
Indicates a change in attention or emphasis from one entity or topic to another.
-
E.
spinOffInfluence
Indicates that one entity has influenced the creation, direction, or characteristics of another entity that is derived from it as a spin-off.
- 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_69ef6a5028108190a14696d9821dde49 |
completed | April 27, 2026, 1:53 p.m. |
| NER | Named-entity recognition | batch_69f63b317e048190963989b732b25b91 |
completed | May 2, 2026, 5:58 p.m. |
| PD | Predicate disambiguation | batch_69f6370ea79c81909b761821ee0fa698 |
completed | May 2, 2026, 5:40 p.m. |
Created at: April 27, 2026, 7:16 p.m.