Triple
T22833351
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | KEWB |
E565867
|
entity |
| Predicate | hasMilitaryTraffic |
P149901
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [KEWB, hasMilitaryTraffic, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasMilitaryTraffic Context triple: [KEWB, hasMilitaryTraffic, true]
-
A.
openedToMilitaryTraffic
Indicates that a route, facility, or passage has been made accessible and available for use by military vehicles or operations.
-
B.
hasMilitaryType
Indicates that an entity is associated with or classified under a specific military category, role, or type.
-
C.
hasMilitaryPresence
Indicates that a military force is present in, stationed at, or operating within a particular location or entity.
-
D.
hasHelicopterTraffic
Indicates that there is regular or notable helicopter movement or operations occurring in or over a given area or location.
-
E.
hasMilitarySecurity
Indicates that an entity provides, maintains, or is responsible for military protection or defense for another entity or area.
- F. None of above. chosen
Provenance (4 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_69e24585ab1c81909b2b5065d15805d5 |
completed | April 17, 2026, 2:36 p.m. |
| NER | Named-entity recognition | batch_69f17e2d830881908d69929b854aad66 |
completed | April 29, 2026, 3:42 a.m. |
| PD | Predicate disambiguation | batch_69eed2d117088190acbfe130d84f8627 |
completed | April 27, 2026, 3:06 a.m. |
| PDg | Predicate description generation | batch_69eeeb577e2081909f4a4e9c296535c0 |
completed | April 27, 2026, 4:51 a.m. |
Created at: April 17, 2026, 3:35 p.m.