Triple
T37358621
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Commendatore |
E927519
|
entity |
| Predicate | invitedToDinnerBy |
P182555
|
FINISHED |
| Object | Don Giovanni |
E272018
|
NE 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: Don Giovanni | Statement: [Commendatore, invitedToDinnerBy, Don Giovanni]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: invitedToDinnerBy Context triple: [Commendatore, invitedToDinnerBy, Don Giovanni]
-
A.
invitesToLocation
Indicates that one entity extends an invitation to another entity to go to or be present at a specific location.
-
B.
guestAtWedding
Indicates that a person is attending or has attended a particular wedding as a guest.
-
C.
invitationBy
chosen
Indicates that one entity is the inviter or originator of an invitation extended to another entity.
-
D.
invitesParticipationOf
Indicates that one entity actively requests or encourages another entity to take part in an activity, event, or process.
-
E.
relationshipWithGuests
Indicates the nature or status of the connection or interaction that someone has with their guests.
- F. None of above.
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_69f76eb701788190b40824bc4594d985 |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_69fb8c38a9688190be524246f5682107 |
completed | May 6, 2026, 6:45 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a40fb6477a48190add270432ad86bb7 |
completed | June 28, 2026, 10:45 a.m. |
| PD | Predicate disambiguation | batch_69fb5a9c6e0481908565bd849e869b24 |
completed | May 6, 2026, 3:13 p.m. |
Created at: May 3, 2026, 4:16 p.m.