Triple
T6941127
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Cairo West Air Base |
E160673
|
entity |
| Predicate | hasAlternateCivilUse |
P32842
|
FINISHED |
| Object | limited civil and government flights |
—
|
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: limited civil and government flights | Statement: [Cairo West Air Base, hasAlternateCivilUse, limited civil and government flights]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasAlternateCivilUse Context triple: [Cairo West Air Base, hasAlternateCivilUse, limited civil and government flights]
-
A.
civilianUse
Indicates that something is intended for, suitable for, or actually used by civilians rather than military or combat purposes.
-
B.
hasSecularUse
Indicates that something is used in a non-religious, worldly, or secular context or purpose.
-
C.
isAlsoUsedAs
chosen
Indicates that something serves an additional function or role beyond its primary one.
-
D.
hasOfficialUse
Indicates that something is used in an authorized or formally recognized capacity, typically by an official body or for official purposes.
-
E.
territorialUse
Indicates the use, control, or occupation of a geographic area or territory by an entity.
- 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_69c6884f3db4819080ad65da69386206 |
completed | March 27, 2026, 1:38 p.m. |
| NER | Named-entity recognition | batch_69c6e0c74fe48190aeaa018631e52ef6 |
completed | March 27, 2026, 7:55 p.m. |
| PD | Predicate disambiguation | batch_69c6d7bd5a388190a57a96d925696ff6 |
completed | March 27, 2026, 7:17 p.m. |
Created at: March 27, 2026, 2:28 p.m.