Triple
T1196905
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 100th Missile Defense Brigade |
E25687
|
entity |
| Predicate | 49th Missile Defense Battalion |
P16565
|
FINISHED |
| Object | based at Fort Greely, Alaska |
—
|
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: based at Fort Greely, Alaska | Statement: [100th Missile Defense Brigade, 49th Missile Defense Battalion, based at Fort Greely, Alaska]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: 49th Missile Defense Battalion Context triple: [100th Missile Defense Brigade, 49th Missile Defense Battalion, based at Fort Greely, Alaska]
-
A.
militaryOrganization
Indicates that an entity functions as, or is associated with, a structured armed forces or defense-related organization.
-
B.
hasMilitaryDivision
Indicates that an entity possesses, includes, or is organizationally associated with a specific military division.
-
C.
squadron
Indicates that an entity is organized into or associated with a specific squadron as a formal operational unit.
-
D.
airDefenseSystemComponent
Indicates that one entity is a component or subsystem of an air defense system associated with another entity.
-
E.
hasBattalion
chosen
Indicates that one entity possesses, commands, or is organizationally assigned a specific battalion.
- 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_69a49429f5ec8190a6a205eb0ae81e5e |
completed | March 1, 2026, 7:31 p.m. |
| NER | Named-entity recognition | batch_69a4bd9a305c819091513394f1b67784 |
completed | March 1, 2026, 10:28 p.m. |
| PD | Predicate disambiguation | batch_69a4bb5d40a08190b7682d8ef8075421 |
completed | March 1, 2026, 10:19 p.m. |
Created at: March 1, 2026, 7:46 p.m.