Triple
T23219089
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Jan Rubens |
E580834
|
entity |
| Predicate | pardonOrReleaseCondition |
P60616
|
FINISHED |
| Object | ban from contact with Anna of Saxony |
—
|
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: ban from contact with Anna of Saxony | Statement: [Jan Rubens, pardonOrReleaseCondition, ban from contact with Anna of Saxony]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: pardonOrReleaseCondition Context triple: [Jan Rubens, pardonOrReleaseCondition, ban from contact with Anna of Saxony]
-
A.
pardonStatus
Indicates whether an entity has been officially forgiven or exempted from penalties for a prior offense or violation.
-
B.
releaseCondition
Indicates the circumstances or requirements under which something is allowed to be released or made available.
-
C.
pardonReason
Indicates the reason or justification for which a pardon is granted.
-
D.
pardonDate
Indicates the date on which an official pardon for an offense is granted or takes effect.
-
E.
restrictionAfterPardon
chosen
Indicates that a restriction or limitation is imposed on an entity following the granting of a pardon.
- 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_69e2460389408190be74f41d217799a9 |
completed | April 17, 2026, 2:38 p.m. |
| NER | Named-entity recognition | batch_69f191675de48190858907872a065c56 |
completed | April 29, 2026, 5:04 a.m. |
| PD | Predicate disambiguation | batch_69effcccee508190a7ae311fdd319806 |
completed | April 28, 2026, 12:18 a.m. |
Created at: April 17, 2026, 4:08 p.m.