Triple
T5573342
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | B-21 Raider |
E146255
|
entity |
| Predicate | stealthTechnology |
P6774
|
FINISHED |
| Object | low observable design |
—
|
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: low observable design | Statement: [B-21 Raider, stealthTechnology, low observable design]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: stealthTechnology Context triple: [B-21 Raider, stealthTechnology, low observable design]
-
A.
trackingTechnology
Indicates that one entity uses or is associated with a technology designed to monitor, record, or follow the behavior, location, or interactions of another entity.
-
B.
technologyType
Indicates the specific kind or category of technology associated with an entity or relationship.
-
C.
technologyUsedIn
Indicates that a particular technology is employed or applied within a specific process, product, context, or domain.
-
D.
technologicalFeature
chosen
Indicates that one entity possesses, exhibits, or is characterized by a specific technological capability, component, or functionality in relation to another entity.
-
E.
laterUsedTechnology
Indicates that one entity adopted or employed a technology after another entity had already used it.
- 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_69c008ffed108190a084602227af6157 |
completed | March 22, 2026, 3:21 p.m. |
| NER | Named-entity recognition | batch_69c02052dd0481909aba6863831357eb |
completed | March 22, 2026, 5:01 p.m. |
| PD | Predicate disambiguation | batch_69c01b147cc081909237f3f2967d4cb8 |
completed | March 22, 2026, 4:38 p.m. |
Created at: March 22, 2026, 3:37 p.m.