Triple
T23738851
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Kevin Bacon as David Lindhagen |
E586610
|
entity |
| Predicate | hasOnScreenConflictWith |
P153502
|
FINISHED |
| Object | Steve Carell as Cal Weaver |
—
|
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: Steve Carell as Cal Weaver | Statement: [Kevin Bacon as David Lindhagen, hasOnScreenConflictWith, Steve Carell as Cal Weaver]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasOnScreenConflictWith Context triple: [Kevin Bacon as David Lindhagen, hasOnScreenConflictWith, Steve Carell as Cal Weaver]
-
A.
hasOnScreenRelative
Indicates that one entity has a family member who appears or is depicted on screen in relation to it.
-
B.
hasOnScreenDynamic
Indicates that one entity displays or presents another entity as a changing or interactive element on a screen.
-
C.
hasScreen
Indicates that an entity is equipped with or includes a screen or display component.
-
D.
hasOnScreenOwner
Indicates that an entity is owned or controlled by another entity that is explicitly shown or represented on screen.
-
E.
hasOnscreenFunction
Indicates that an entity serves a particular role or performs a specific function when it appears on screen.
- 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_69e24907dc9c8190be074c9c96a0ec2d |
completed | April 17, 2026, 2:51 p.m. |
| NER | Named-entity recognition | batch_69f1bad427f081908eaf96273fec757b |
completed | April 29, 2026, 8:01 a.m. |
| PD | Predicate disambiguation | batch_69f155f012808190a4b1cbc155558ade |
completed | April 29, 2026, 12:50 a.m. |
| PDg | Predicate description generation | batch_69f15adb23d88190ac2632299c26a9b3 |
completed | April 29, 2026, 1:11 a.m. |
Created at: April 17, 2026, 7:11 p.m.