Triple
T27243670
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Beale Air Force Base |
E687278
|
entity |
| Predicate | hasMilitaryCategory |
P164186
|
FINISHED |
| Object | military air base |
—
|
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: military air base | Statement: [Beale Air Force Base, hasMilitaryCategory, military air base]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasMilitaryCategory Context triple: [Beale Air Force Base, hasMilitaryCategory, military air base]
-
A.
hasMilitaryType
Indicates that an entity is associated with or classified under a specific military category, role, or type.
-
B.
hasMilitaryClass
chosen
Indicates that an entity belongs to, is assigned to, or is categorized under a specific military class or classification.
-
C.
hasMilitarySecurity
Indicates that an entity provides, maintains, or is responsible for military protection or defense for another entity or area.
-
D.
hasMilitaryDesignation
Indicates that an entity is assigned a specific military-related code, title, or classification.
-
E.
hasMilitaryAssociation
Indicates a relationship in which an entity is connected or affiliated with a military organization, activity, or function.
- 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_69ef355547408190b5ca0d777c65040a |
completed | April 27, 2026, 10:07 a.m. |
| NER | Named-entity recognition | batch_69f6a8df16a88190a23820e64a3b1f92 |
completed | May 3, 2026, 1:46 a.m. |
| PD | Predicate disambiguation | batch_69f6a751d5e48190a77dcecbe7ef9f0b |
completed | May 3, 2026, 1:39 a.m. |
Created at: April 27, 2026, 10:39 a.m.