Triple
T19282066
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Space Delta 11 |
E482213
|
entity |
| Predicate | shortName |
P43
|
FINISHED |
| Object | DEL 11 |
—
|
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: DEL 11 | Statement: [Space Delta 11, shortName, DEL 11]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: DEL 11 Context triple: [Space Delta 11, shortName, DEL 11]
-
A.
DEL 11
chosen
DEL 11 is a U.S. Space Force unit, formally known as Space Delta 11, responsible for training and readiness in space operations.
-
B.
DEL 10
DEL 10 is a United States Space Force unit focused on space domain awareness and related space operations.
-
C.
DEL 4
DEL 4 is a U.S. Space Force unit responsible for missile warning and related space operations.
-
D.
DEL 3
DEL 3 is a United States Space Force unit, formally known as Space Delta 3, responsible for space electromagnetic warfare operations.
-
E.
DEL 7
DEL 7 is a U.S. Space Force unit, formally known as Space Delta 7, responsible for conducting intelligence, surveillance, and reconnaissance operations in the space domain.
- F. None of above.
- G. Unsure - the case is ambiguous/there is not enough information to decide.
Provenance (2 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_69d8e8cf61b0819096fe3e4107827c4e |
completed | April 10, 2026, 12:10 p.m. |
| NER | Named-entity recognition | batch_69e5fbff1e6c819094ae6a5ad40adb65 |
completed | April 20, 2026, 10:12 a.m. |
Created at: April 10, 2026, 1:30 p.m.