Triple
T28770189
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Dumb and Dumberer: When Harry Met Lloyd |
E726388
|
entity |
| Predicate | hasNewCastRelativeTo |
P121003
|
FINISHED |
| Object | Dumb and Dumber |
—
|
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: Dumb and Dumber | Statement: [Dumb and Dumberer: When Harry Met Lloyd, hasNewCastRelativeTo, Dumb and Dumber]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasNewCastRelativeTo Context triple: [Dumb and Dumberer: When Harry Met Lloyd, hasNewCastRelativeTo, Dumb and Dumber]
-
A.
hasCast
Indicates that a creative work features a particular group of performers or actors.
-
B.
hasMainCastChange
chosen
Indicates that the primary cast of a work has changed at some point (e.g., key main characters or actors were replaced, added, or removed).
-
C.
hasRelativeInCast
Indicates that an individual has a family member who is part of the cast of a given production.
-
D.
hasCasting
Indicates that an entity features a particular actor or set of actors in its cast.
-
E.
hasMinimalCast
Indicates that an entity (such as a film or production) involves only a small or minimal number of cast members.
- 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_69f03198be14819098fa74e48b3749bf |
completed | April 28, 2026, 4:03 a.m. |
| NER | Named-entity recognition | batch_69fdb31800508190beec15adb9bbd292 |
completed | May 8, 2026, 9:55 a.m. |
| PD | Predicate disambiguation | batch_69fdb19c381c8190bafb2f565da097f1 |
completed | May 8, 2026, 9:49 a.m. |
Created at: April 28, 2026, 6:15 a.m.