Triple
T28921732
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Matthew (Four Weddings and a Funeral) |
E733531
|
entity |
| Predicate | toneOfEulogy |
P165524
|
FINISHED |
| Object | tender and heartbreaking |
—
|
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: tender and heartbreaking | Statement: [Matthew (Four Weddings and a Funeral), toneOfEulogy, tender and heartbreaking]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: toneOfEulogy Context triple: [Matthew (Four Weddings and a Funeral), toneOfEulogy, tender and heartbreaking]
-
A.
typeOfSpeechDelivered
Indicates that a specific kind or category of speech (e.g., keynote, lecture, toast) was delivered in a given event or context.
-
B.
isPosthumousTributeTo
Indicates that something (such as a work, event, or honor) is created or given as a tribute to a person after that person has died.
-
C.
typeOfTribute
Indicates the specific kind or category of tribute that is being given or required in a relationship.
-
D.
typeOfPraise
Indicates a specific kind or category of praise being expressed or applied in a given context.
-
E.
recordedTributeFrom
Indicates that one entity documented or registered the receipt of tribute from another entity.
- 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_69f05b0a5cc0819094828367ae204b70 |
completed | April 28, 2026, 7 a.m. |
| NER | Named-entity recognition | batch_69f65b1b09a08190934a1b04d6381028 |
completed | May 2, 2026, 8:14 p.m. |
| PD | Predicate disambiguation | batch_69f6576487e081908d802f1caf59c423 |
completed | May 2, 2026, 7:58 p.m. |
| PDg | Predicate description generation | batch_69f65875030881909007c502b7dcc998 |
completed | May 2, 2026, 8:03 p.m. |
Created at: April 28, 2026, 8:20 a.m.