Triple
T21996374
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Papal conclave, 1730 |
E543215
|
entity |
| Predicate | triggeredByEvent |
P55105
|
FINISHED |
| Object | death of Benedict XIII on 1730-02-21 |
—
|
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: death of Benedict XIII on 1730-02-21 | Statement: [Papal conclave, 1730, triggeredByEvent, death of Benedict XIII on 1730-02-21]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: triggeredByEvent Context triple: [Papal conclave, 1730, triggeredByEvent, death of Benedict XIII on 1730-02-21]
-
A.
triggerEvent
Indicates that one entity causes or initiates the occurrence of a specific event involving another entity or the system.
-
B.
triggered
Indicates that one entity causes an event, action, or process involving another entity to start or occur.
-
C.
triggeredFrom
chosen
Indicates that one event, action, or process was initiated or caused as a result of another specific event, action, or process.
-
D.
trigger
Indicates that one entity causes or initiates an event, state, or action in another entity or system.
-
E.
basedOnEvent
Indicates that something is derived from, influenced by, or determined in reference to a specific event.
- 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_69e11e2c814c8190837d072789000486 |
completed | April 16, 2026, 5:36 p.m. |
| NER | Named-entity recognition | batch_69f12765fb0c81908f7b7acda065ee2f |
completed | April 28, 2026, 9:32 p.m. |
| PD | Predicate disambiguation | batch_69e6f62dc9d88190ae387f145f9528de |
completed | April 21, 2026, 3:59 a.m. |
Created at: April 16, 2026, 8:19 p.m.