Triple
T29954533
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Newlyweds |
E760857
|
entity |
| Predicate | directorAlsoActor |
P51493
|
FINISHED |
| Object | Edward Burns |
—
|
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: Edward Burns | Statement: [Newlyweds, directorAlsoActor, Edward Burns]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: directorAlsoActor Context triple: [Newlyweds, directorAlsoActor, Edward Burns]
-
A.
directorOfWorkFeaturingSubject
Indicates that the subject is the director of a creative work in which another specified entity appears or is featured.
-
B.
directorSpouseInCast
Indicates that a film’s director is married to someone who appears as a cast member in that same film.
-
C.
directorAssociatedWith
Indicates a relationship where a director is professionally connected to, responsible for, or involved with a particular entity (such as a work, organization, or project).
-
D.
filmCoStar
Indicates that two people appeared together as co-actors in the same film.
-
E.
leadActorAlsoDirector
chosen
Indicates that the person who plays the lead acting role in a production is also the director of that same production.
- 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_69f2246562b881909d57622f4086d43d |
completed | April 29, 2026, 3:31 p.m. |
| NER | Named-entity recognition | batch_69fbbc49da8c8190902bbb05d2477cab |
completed | May 6, 2026, 10:10 p.m. |
| PD | Predicate disambiguation | batch_69fbb13f34b08190bbbb220ac1e6e666 |
completed | May 6, 2026, 9:23 p.m. |
Created at: April 29, 2026, 6:27 p.m.