Triple
T9278758
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Prince-Bishopric of Trent |
E223014
|
entity |
| Predicate | notableEventStart |
P925
|
FINISHED |
| Object | 1545 |
—
|
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: 1545 | Statement: [Prince-Bishopric of Trent, notableEventStart, 1545]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: notableEventStart Context triple: [Prince-Bishopric of Trent, notableEventStart, 1545]
-
A.
notableEventResponse
Indicates a response, reaction, or consequence that occurs as a result of a notable event.
-
B.
notableEventDate
chosen
Indicates the date on which a notable or significant event associated with the subject occurred.
-
C.
notableSubevent
Indicates that one event is a particularly significant or noteworthy component within a larger, encompassing event.
-
D.
capitalEventDate
Indicates the date on which a capital-related event (such as establishment, designation, or change of capital status) occurred.
-
E.
notableEventInLife
Indicates that a particular event holds significant importance or impact within an entity’s life or personal history.
- 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_69ca842123588190b3f2e1a69037d141 |
completed | March 30, 2026, 2:09 p.m. |
| NER | Named-entity recognition | batch_69cd07cb28e081909b2754756c8f5dd0 |
completed | April 1, 2026, 11:55 a.m. |
| PD | Predicate disambiguation | batch_69cc7a576ec88190bbb787eb82e2e539 |
completed | April 1, 2026, 1:52 a.m. |
Created at: March 30, 2026, 7:34 p.m.