Triple
T31225183
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Iraqi Marine Corps |
E796117
|
entity |
| Predicate | notableFacilityGuarded |
P64110
|
FINISHED |
| Object | Al Basrah Oil Terminal |
E1951825
|
NE 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: Al Basrah Oil Terminal | Statement: [Iraqi Marine Corps, notableFacilityGuarded, Al Basrah Oil Terminal]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: notableFacilityGuarded Context triple: [Iraqi Marine Corps, notableFacilityGuarded, Al Basrah Oil Terminal]
-
A.
notableLocationGuarded
chosen
Indicates that a notable or significant location is being actively protected or guarded by an entity.
-
B.
isSecureFacility
Indicates that a facility has protections, controls, and safeguards in place to prevent unauthorized access, tampering, or security breaches.
-
C.
hasHighSecurityFacility
Indicates that an entity possesses or operates a facility characterized by a high level of security measures and protections.
-
D.
residenceGuarded
Indicates that a residence is being actively protected or watched over, typically for security purposes.
-
E.
withinFortifications
Indicates that one entity is located inside the defensive structures or fortifications of another entity.
- F. None of above.
Provenance (4 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_69f224da98f88190ab32f690cce5d303 |
completed | April 29, 2026, 3:33 p.m. |
| NER | Named-entity recognition | batch_6a037c876524819098545e6037d3107d |
completed | May 12, 2026, 7:16 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a2a1e1cae7081908f4ca6ec3cf661d8 |
completed | June 11, 2026, 2:31 a.m. |
| PD | Predicate disambiguation | batch_6a0379e5174c8190a0bdde7e381b7624 |
completed | May 12, 2026, 7:05 p.m. |
Created at: April 29, 2026, 9:10 p.m.