Triple
T33184851
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Calvada Productions |
E849437
|
entity |
| Predicate | associatedShowStar |
P154567
|
FINISHED |
| Object | Dick Van Dyke |
E74544
|
NE 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: Dick Van Dyke | Statement: [Calvada Productions, associatedShowStar, Dick Van Dyke]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: associatedShowStar Context triple: [Calvada Productions, associatedShowStar, Dick Van Dyke]
-
A.
associatedShow
Indicates a relationship where one entity is linked or connected to a particular show (e.g., as its subject, source, or related program).
-
B.
associatedWithLeadActorsOfSeries
chosen
Indicates a relationship where something or someone is connected or linked to the lead actors of a television or film series.
-
C.
associatedShowType
Indicates a relationship where one entity is linked to the type or category of show with which it is associated.
-
D.
starredActor
Indicates that an actor performed a leading or significant role in a particular production or work.
-
E.
starredActorWith
Indicates that one entity participated as an actor in a production together with another specified actor.
- F. None of above.
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_69f3495e0f108190a6a7006f79f9c2c3 |
completed | April 30, 2026, 12:21 p.m. |
| NER | Named-entity recognition | batch_6a037c894b488190bcbec2eccaff4a01 |
completed | May 12, 2026, 7:16 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a352fba63c88190b2bc3501bb2dac83 |
completed | June 19, 2026, 12:02 p.m. |
| PD | Predicate disambiguation | batch_6a0379f338b881908e5593e45d764f4d |
completed | May 12, 2026, 7:05 p.m. |
Created at: May 1, 2026, 1:29 a.m.