Triple
T29174720
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Minot Air Force Base |
E739574
|
entity |
| Predicate | missileComplexArea |
P170733
|
FINISHED |
| Object | north-central North Dakota |
—
|
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: north-central North Dakota | Statement: [Minot Air Force Base, missileComplexArea, north-central North Dakota]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: missileComplexArea Context triple: [Minot Air Force Base, missileComplexArea, north-central North Dakota]
-
A.
missileLaunchCapability
Indicates that an entity has the ability or functionality to launch missiles.
-
B.
airDefenceSector
Indicates a relationship where an entity is assigned to, located in, or associated with a specific air defence sector responsible for airspace protection and control.
-
C.
airDefenseSystem
Indicates a defensive military system designed to detect, track, and engage airborne threats such as aircraft or missiles.
-
D.
airDefenseSystemComponent
Indicates that one entity is a component or subsystem of an air defense system associated with another entity.
-
E.
missileFamily
Indicates that one missile belongs to, or is categorized within, the same family or series as another missile.
- 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_69f07cb6394c8190ab7842c48e699e2a |
completed | April 28, 2026, 9:24 a.m. |
| NER | Named-entity recognition | batch_69f695f9fe7c819084322bf6cdc70a13 |
completed | May 3, 2026, 12:25 a.m. |
| PD | Predicate disambiguation | batch_69f690ed5d008190831cf8e44cce28af |
completed | May 3, 2026, 12:03 a.m. |
| PDg | Predicate description generation | batch_69f695385a2881908cc28ef97fffc867 |
completed | May 3, 2026, 12:22 a.m. |
Created at: April 28, 2026, 11:54 a.m.