Triple
T26138096
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | منف |
E659435
|
entity |
| Predicate | لها_دور_عسكري |
P9463
|
FINISHED |
| Object | قاعدة عسكرية استراتيجية |
—
|
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: قاعدة عسكرية استراتيجية | Statement: [منف, لها_دور_عسكري, قاعدة عسكرية استراتيجية]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: لها_دور_عسكري Context triple: [منف, لها_دور_عسكري, قاعدة عسكرية استراتيجية]
-
A.
militaryRole
chosen
Indicates the specific function, position, or duty an entity holds within a military organization or context.
-
B.
従軍先
Indicates the location or destination where someone is deployed or serves in the military.
-
C.
hadMilitaryPost
Indicates that an entity held an official position or assignment within a military organization.
-
D.
militaryTheater
Indicates that an entity is a geographic or operational area where military operations or campaigns are conducted.
-
E.
roleInWarOrConflict
Indicates the specific function, position, or involvement an entity has within a particular war or conflict.
- 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_69ee5bc3c20c8190bf2cf272f4170e95 |
completed | April 26, 2026, 6:38 p.m. |
| NER | Named-entity recognition | batch_69f60be1d2408190820365bf7d8436bd |
completed | May 2, 2026, 2:36 p.m. |
| PD | Predicate disambiguation | batch_69f5f7fd90fc81909055b211368f9139 |
completed | May 2, 2026, 1:11 p.m. |
Created at: April 26, 2026, 8:18 p.m.