Triple
T15948686
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 131st Bomb Wing |
E386755
|
entity |
| Predicate | hasAircraftFeature |
P51088
|
FINISHED |
| Object | low radar cross-section |
—
|
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 radar cross-section | Statement: [131st Bomb Wing, hasAircraftFeature, low radar cross-section]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasAircraftFeature Context triple: [131st Bomb Wing, hasAircraftFeature, low radar cross-section]
-
A.
aircraftCapability
chosen
Indicates that an aircraft possesses a particular capability, function, or operational feature.
-
B.
airCapability
Indicates that an entity possesses the ability or resources to operate or project power in the air (e.g., through aircraft, air defenses, or related systems).
-
C.
hasBasedAircraft
Indicates that an aircraft is regularly stationed or primarily based at a particular location or facility.
-
D.
flightDeckFeature
Indicates that one entity is a feature, component, or element that is part of or present on the flight deck of another entity.
-
E.
supportsAircraft
Indicates that one entity is capable of accommodating, carrying, or enabling the operation of an aircraft.
- 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_69d86da882448190a82ea962fe343b79 |
completed | April 10, 2026, 3:25 a.m. |
| NER | Named-entity recognition | batch_69e17d4d08f481909f38b75e3f42d9ab |
completed | April 17, 2026, 12:22 a.m. |
| PD | Predicate disambiguation | batch_69e142d37cd88190ab50760f1783e20c |
completed | April 16, 2026, 8:13 p.m. |
Created at: April 10, 2026, 4:53 a.m.