Triple
T6670638
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Siege of Arrah |
E151718
|
entity |
| Predicate | reliefOutcome |
P68009
|
FINISHED |
| Object | successful relief of the besieged garrison |
—
|
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: successful relief of the besieged garrison | Statement: [Siege of Arrah, reliefOutcome, successful relief of the besieged garrison]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: reliefOutcome Context triple: [Siege of Arrah, reliefOutcome, successful relief of the besieged garrison]
-
A.
reliefGranted
Indicates that a requested form of assistance, exemption, or remedy has been officially approved and provided.
-
B.
relief
chosen
Indicates a state or action in which distress, pain, or difficulty is reduced, eased, or removed for an entity.
-
C.
legalOutcome
Indicates the resulting legal status, decision, or consequence that follows from a legal process, action, or judgment.
-
D.
relievedBy
Indicates that one entity eases, reduces, or removes the burden, pain, stress, or responsibility experienced by another entity.
-
E.
reasonForRelief
Indicates the cause, justification, or circumstance that explains why relief or alleviation from a condition or obligation 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_69c687f71fc081909dbd45d6377f6045 |
completed | March 27, 2026, 1:36 p.m. |
| NER | Named-entity recognition | batch_69c6ce738fe88190a5557900efeec7ec |
completed | March 27, 2026, 6:37 p.m. |
| PD | Predicate disambiguation | batch_69c6ad09974c81908784300ae218961f |
completed | March 27, 2026, 4:15 p.m. |
Created at: March 27, 2026, 2:03 p.m.