Triple
T1233924
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Siege of Leiden |
E26504
|
entity |
| Predicate | dateOfRelief |
P14067
|
FINISHED |
| Object | 1574-10-03 |
—
|
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: 1574-10-03 | Statement: [Siege of Leiden, dateOfRelief, 1574-10-03]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: dateOfRelief Context triple: [Siege of Leiden, dateOfRelief, 1574-10-03]
-
A.
relievedOnDate
Indicates that an entity was formally released, discharged, or relieved from a role, duty, or obligation on a specific date.
-
B.
liberationDate
chosen
Indicates the date on which an entity was freed, released, or liberated from a prior state of control, confinement, or oppression.
-
C.
hasReliefOf
Indicates that one entity features, bears, or is adorned with a sculpted or carved relief representation of another entity.
-
D.
releaseOf
Indicates the act or event of something being set free, made available, or discharged from a prior state of containment, control, or restriction.
-
E.
relievedBy
Indicates that one entity eases, reduces, or removes the burden, pain, stress, or responsibility experienced by another entity.
- 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_69a4948571c88190a9191e451e6035fd |
completed | March 1, 2026, 7:33 p.m. |
| NER | Named-entity recognition | batch_69a4be5d16ec819088056167c88d3318 |
completed | March 1, 2026, 10:31 p.m. |
| PD | Predicate disambiguation | batch_69a4bb65d61c8190bf0424ea0019a98b |
completed | March 1, 2026, 10:19 p.m. |
Created at: March 1, 2026, 7:47 p.m.