Triple
T6987774
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Guy de Montfort, Count of Nola |
E162006
|
entity |
| Predicate | placeOfMurderCommitted |
P64889
|
FINISHED |
| Object | church at Viterbo |
—
|
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: church at Viterbo | Statement: [Guy de Montfort, Count of Nola, placeOfMurderCommitted, church at Viterbo]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: placeOfMurderCommitted Context triple: [Guy de Montfort, Count of Nola, placeOfMurderCommitted, church at Viterbo]
-
A.
placeOfKilling
chosen
Indicates the location where a killing event took place.
-
B.
placeOfExecution
Indicates the location where an execution or carrying out of a sentence, order, or legal punishment took place.
-
C.
reasonForMurder
Indicates the motive or underlying cause that led someone to commit a murder.
-
D.
assassinationAttemptLocation
Indicates the place where an attempted assassination occurred or was intended to occur.
-
E.
positionOnCrime
Indicates a stance, opinion, or policy position that an entity holds regarding crime or crime-related issues.
- 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_69c68856d7808190ab33ee914640281b |
completed | March 27, 2026, 1:38 p.m. |
| NER | Named-entity recognition | batch_69c6dbbd926c8190a8b60527bd553fa3 |
completed | March 27, 2026, 7:34 p.m. |
| PD | Predicate disambiguation | batch_69c6d7c4a18881908d267137daed828b |
completed | March 27, 2026, 7:17 p.m. |
Created at: March 27, 2026, 2:32 p.m.