Triple
T28413348
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Gakona, Alaska |
E719727
|
entity |
| Predicate | HAARPFormerOperator |
P31764
|
FINISHED |
| Object | United States Air Force |
—
|
NE NERFINISHED |
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: United States Air Force | Statement: [Gakona, Alaska, HAARPFormerOperator, United States Air Force]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: HAARPFormerOperator Context triple: [Gakona, Alaska, HAARPFormerOperator, United States Air Force]
-
A.
HAARPFunction
Indicates the operational role, purpose, or primary activity performed by the HAARP system or facility.
-
B.
formerOperates
chosen
Indicates that an entity previously operated or managed another entity but no longer does so.
-
C.
callsignOfOperator
Indicates that one entity is the radio or communication callsign assigned to or used by another entity acting as an operator.
-
D.
missionOperator
Indicates that one entity is responsible for operating, managing, or controlling a mission involving another entity.
-
E.
hostSpacecraftOperator
Indicates that one entity operates or manages the spacecraft that is being hosted or carried by another 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_69eff6f0f37c8190b37bc6fab08a9449 |
completed | April 27, 2026, 11:53 p.m. |
| NER | Named-entity recognition | batch_69f64e37f7fc819083809149b6661e3c |
completed | May 2, 2026, 7:19 p.m. |
| PD | Predicate disambiguation | batch_69f64caede108190a35cc7cbfead866f |
completed | May 2, 2026, 7:12 p.m. |
Created at: April 28, 2026, 1:28 a.m.