Triple
T24282753
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Siege of Abadan |
E605587
|
entity |
| Predicate | defensiveOutcome |
P82243
|
FINISHED |
| Object | Iran maintained control of Abadan |
—
|
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: Iran maintained control of Abadan | Statement: [Siege of Abadan, defensiveOutcome, Iran maintained control of Abadan]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: defensiveOutcome Context triple: [Siege of Abadan, defensiveOutcome, Iran maintained control of Abadan]
-
A.
defensiveSuccess
chosen
Indicates that a defensive action successfully prevented or mitigated an opposing threat, attack, or adverse outcome.
-
B.
defensivePlayerInvolved
Indicates that a defensive player participates in or is directly involved in a particular play, event, or defensive action.
-
C.
usedDefensiveLine
Indicates that an entity employed or deployed a particular defensive line as part of its strategy or actions.
-
D.
defensiveRole
Indicates that an entity serves a protective or guarding function in relation to another entity or context.
-
E.
usedAsDefensiveLineAgainst
Indicates that something functions as a protective barrier or line of defense against a specified opposing force or threat.
- 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_69e295480d0c8190846fc3c2e2da1d4c |
completed | April 17, 2026, 8:17 p.m. |
| NER | Named-entity recognition | batch_69f28f52e57c8190ab73e4b2b6a9eafd |
completed | April 29, 2026, 11:08 p.m. |
| PD | Predicate disambiguation | batch_69f1c457a2908190993824395b3c365d |
completed | April 29, 2026, 8:41 a.m. |
Created at: April 18, 2026, 12:08 a.m.