Triple
T23680239
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Carlo Gesualdo |
E584997
|
entity |
| Predicate | homicidePlace |
P64889
|
FINISHED |
| Object | Palazzo San Severo, Naples |
—
|
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: Palazzo San Severo, Naples | Statement: [Carlo Gesualdo, homicidePlace, Palazzo San Severo, Naples]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: homicidePlace Context triple: [Carlo Gesualdo, homicidePlace, Palazzo San Severo, Naples]
-
A.
placeOfKilling
chosen
Indicates the location where a killing event took place.
-
B.
assassinatedIn
Indicates that an assassination of one entity occurred within the specified location or context represented by another entity.
-
C.
assassinationAttemptLocation
Indicates the place where an attempted assassination occurred or was intended to occur.
-
D.
notableMassKillingSite
Indicates that a place is recognized as a significant location where a mass killing or massacre occurred.
-
E.
hasMurderer
Indicates that one entity is the person who committed the murder of another 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_69e24901f7c08190909fd727632e823d |
completed | April 17, 2026, 2:51 p.m. |
| NER | Named-entity recognition | batch_69f1b4f73148819089fa0c1a437f91fe |
completed | April 29, 2026, 7:36 a.m. |
| PD | Predicate disambiguation | batch_69f118dd13008190a8799b4e9cadbd79 |
completed | April 28, 2026, 8:30 p.m. |
Created at: April 17, 2026, 6:51 p.m.