Triple
T14489858
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Exsurge Domine et judica causam tuam |
E359331
|
entity |
| Predicate | givesDeadlineFor |
P22598
|
FINISHED |
| Object | recantation of condemned propositions |
—
|
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: recantation of condemned propositions | Statement: [Exsurge Domine et judica causam tuam, givesDeadlineFor, recantation of condemned propositions]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: givesDeadlineFor Context triple: [Exsurge Domine et judica causam tuam, givesDeadlineFor, recantation of condemned propositions]
-
A.
hasDeadline
Indicates that an entity is associated with a specific due date or time by which it must be completed or fulfilled.
-
B.
notificationDeadline
Indicates the time or date by which a required notification must be sent or received.
-
C.
dateOfUltimatum
chosen
Indicates the specific date on which an ultimatum was issued, delivered, or came into effect in the relationship between the involved parties.
-
D.
awardedUntil
Indicates that an award, recognition, or similar honor is valid or in effect for a recipient up to and including a specified end time or date.
-
E.
finalDeliveryDate
Indicates the date on which the last or ultimate delivery in a sequence of deliveries is scheduled or actually occurs.
- 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_69d8279740308190af9df93a3af8592e |
completed | April 9, 2026, 10:26 p.m. |
| NER | Named-entity recognition | batch_69de930bd1d48190abd6c47da0a3ebc8 |
completed | April 14, 2026, 7:18 p.m. |
| PD | Predicate disambiguation | batch_69de5c487b4c819097803e58dca628a5 |
completed | April 14, 2026, 3:24 p.m. |
Created at: April 10, 2026, 1:20 a.m.