Triple
T1678016
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Four Weddings and a Funeral |
E36275
|
entity |
| Predicate | screenDebutFor |
P26909
|
FINISHED |
| Object | no major debuts |
—
|
LITERAL 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: no major debuts | Statement: [Four Weddings and a Funeral, screenDebutFor, no major debuts]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: screenDebutFor Context triple: [Four Weddings and a Funeral, screenDebutFor, no major debuts]
-
A.
screenDebut
chosen
Indicates the event or relationship in which an entity appears on screen for the first time in a film, television, or other visual media production.
-
B.
displays
Indicates that one entity visually presents or shows another entity’s content or information.
-
C.
presentedFor
Indicates that one entity was formally offered, submitted, or shown to another entity for consideration, review, or action.
-
D.
showsThat
Indicates that one entity demonstrates, proves, or provides evidence for the truth or validity of another.
-
E.
presentedBy
Indicates that something (such as an event, performance, or work) is formally organized, hosted, or introduced by a particular person or entity.
- 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_69a886139ed081909af0940aa9313512 |
completed | March 4, 2026, 7:20 p.m. |
| NER | Named-entity recognition | batch_69aba644070c81908745b56d981fe273 |
completed | March 7, 2026, 4:15 a.m. |
| PD | Predicate disambiguation | batch_69aa61b57a6881909373af287ef24799 |
completed | March 6, 2026, 5:10 a.m. |
Created at: March 4, 2026, 7:29 p.m.