Triple
T29954541
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Newlyweds |
E760857
|
entity |
| Predicate | hasDirectorScreenwriterCombination |
P150712
|
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, hasDirectorScreenwriterCombination, Edward Burns]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasDirectorScreenwriterCombination Context triple: [Newlyweds, hasDirectorScreenwriterCombination, Edward Burns]
-
A.
hasDirectorScreenwriter
chosen
Indicates that a director is also the screenwriter (or one of the screenwriters) for a given work.
-
B.
hasDirectorWriterCombination
Indicates that a specific combination of director and writer is associated with a particular work or production.
-
C.
hasAuthorDirector
Indicates that an entity (such as a work or production) has a person who serves in both the roles of author and director for it.
-
D.
hasDirectorStar
Indicates that a person both directed and starred in the same work (e.g., film, show, or production).
-
E.
leadActorAlsoDirector
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_69fd509e6bc08190b263923c2f40fea3 |
completed | May 8, 2026, 2:55 a.m. |
| PD | Predicate disambiguation | batch_69fd4fd1a58881909d4b84de1b24e380 |
completed | May 8, 2026, 2:52 a.m. |
Created at: April 29, 2026, 6:27 p.m.