Triple
T5215890
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Khorramshahr |
E117750
|
entity |
| Predicate | borderConflict |
P49394
|
FINISHED |
| Object | territorial disputes between Iran and Iraq |
—
|
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: territorial disputes between Iran and Iraq | Statement: [Khorramshahr, borderConflict, territorial disputes between Iran and Iraq]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: borderConflict Context triple: [Khorramshahr, borderConflict, territorial disputes between Iran and Iraq]
-
A.
borderDisputesWith
chosen
Indicates that there are contested or unresolved boundary claims between two entities.
-
B.
borderConcern
Indicates a relationship where one entity has issues, disputes, or security considerations related to its shared boundary or border with another entity.
-
C.
conflictBelligerent
Indicates that an entity is a participating belligerent (e.g., a country, group, or force) in a specific conflict.
-
D.
conflictRegion
Indicates that the entities are located in or associated with a geographic area characterized by active or recent conflict, tension, or hostilities.
-
E.
conflictIn
Indicates that one entity is involved in, associated with, or occurs within a particular conflict or dispute.
- 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_69bd4464ba3c8190bc16b2ebbe42ddb0 |
completed | March 20, 2026, 12:58 p.m. |
| NER | Named-entity recognition | batch_69bd7a93fcc08190a1d2d025b4365d5a |
completed | March 20, 2026, 4:49 p.m. |
| PD | Predicate disambiguation | batch_69bd77bb4e8c819094b5ac7cf61512f9 |
completed | March 20, 2026, 4:37 p.m. |
Created at: March 20, 2026, 1:48 p.m.