Triple
T28707308
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Charles (Four Weddings and a Funeral) |
E729728
|
entity |
| Predicate | weddingAttended |
P76666
|
FINISHED |
| Object | Angus and Laura's wedding |
—
|
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: Angus and Laura's wedding | Statement: [Charles (Four Weddings and a Funeral), weddingAttended, Angus and Laura's wedding]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: weddingAttended Context triple: [Charles (Four Weddings and a Funeral), weddingAttended, Angus and Laura's wedding]
-
A.
guestAtWedding
chosen
Indicates that a person is attending or has attended a particular wedding as a guest.
-
B.
hasAttended
Indicates that an entity has been present at or participated in a particular event, place, or gathering.
-
C.
associatedWithWeddingOf
Indicates a relationship where something is connected or related to the wedding event of specific individuals.
-
D.
weddingStatus
Indicates the current state or condition of an entity’s marriage or wedding (e.g., single, engaged, married, divorced).
-
E.
hasPublicCeremony
Indicates that a public ceremony is held or conducted in relation to the subject 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_69f043e7d5a4819094b18aca10b1e024 |
completed | April 28, 2026, 5:21 a.m. |
| NER | Named-entity recognition | batch_69f656d4e7b081909ba541afc649a059 |
completed | May 2, 2026, 7:56 p.m. |
| PD | Predicate disambiguation | batch_69f651ac855481908e30c3b345d31356 |
completed | May 2, 2026, 7:34 p.m. |
Created at: April 28, 2026, 5:46 a.m.