Triple
T6185160
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Western Iraq |
E138036
|
entity |
| Predicate | hasMilitaryImportance |
P27512
|
FINISHED |
| Object | control of border crossings |
—
|
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: control of border crossings | Statement: [Western Iraq, hasMilitaryImportance, control of border crossings]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasMilitaryImportance Context triple: [Western Iraq, hasMilitaryImportance, control of border crossings]
-
A.
hasMilitarySignificance
chosen
Indicates that something holds strategic or tactical importance for military planning, operations, or defense objectives.
-
B.
militaryImportance
Indicates the degree to which something is strategically or operationally significant to military objectives or capabilities.
-
C.
hasMilitarySignificanceSince
Indicates that something has held military importance or strategic value starting from a specified point in time.
-
D.
hasMilitaryBase
Indicates that one entity possesses, hosts, or contains a military base associated with or located on another entity.
-
E.
militaryUse
Indicates the use of something (such as land, facilities, equipment, or resources) for military purposes or operations.
- 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_69c008a8fd408190b7ec6e42934974a6 |
completed | March 22, 2026, 3:20 p.m. |
| NER | Named-entity recognition | batch_69c062150fc48190877240abe6b6c636 |
completed | March 22, 2026, 9:41 p.m. |
| PD | Predicate disambiguation | batch_69c055fa0a808190bda37832e3ac150c |
completed | March 22, 2026, 8:50 p.m. |
Created at: March 22, 2026, 4:19 p.m.