Triple
T17584677
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Space Delta 3 |
E428291
|
entity |
| Predicate | abbreviation |
P43
|
FINISHED |
| Object | DEL 3 |
—
|
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 3 | Statement: [Space Delta 3, abbreviation, DEL 3]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: DEL 3 Context triple: [Space Delta 3, abbreviation, DEL 3]
-
A.
DEL 3
chosen
DEL 3 is a United States Space Force unit, formally known as Space Delta 3, responsible for space electromagnetic warfare operations.
-
B.
DEL 4
DEL 4 is a U.S. Space Force unit responsible for missile warning and related space operations.
-
C.
DEL 6
DEL 6 is a U.S. Space Force unit responsible for conducting and overseeing space-based cyber and communications operations.
-
D.
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.
-
E.
DEL 11
DEL 11 is a U.S. Space Force unit, formally known as Space Delta 11, responsible for training and readiness in space operations.
- 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_69d889e1030481909950e140c63255b9 |
completed | April 10, 2026, 5:25 a.m. |
| NER | Named-entity recognition | batch_69e463d113b08190975506f3558c1eca |
completed | April 19, 2026, 5:10 a.m. |
Created at: April 10, 2026, 5:50 a.m.