Triple
T14164446
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | 509th Bomb Wing |
E351033
|
entity |
| Predicate | typeOfBomberForce |
P6154
|
FINISHED |
| Object | long-range bomber unit |
—
|
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: long-range bomber unit | Statement: [509th Bomb Wing, typeOfBomberForce, long-range bomber unit]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: typeOfBomberForce Context triple: [509th Bomb Wing, typeOfBomberForce, long-range bomber unit]
-
A.
mainBomberAircraft
Indicates that an entity serves as the primary bomber aircraft used by another entity (such as a military force, operation, or country).
-
B.
enemyForceType
Indicates that one entity is characterized as a hostile or opposing force of a specified type relative to another entity.
-
C.
fleetType
Indicates the category or classification of a fleet to which an entity belongs or with which it is associated.
-
D.
isMilitaryAssetOf
Indicates that something functions as a military resource, equipment, or facility that belongs to, is controlled by, or is used by a particular entity.
-
E.
typeOfTroops
chosen
Indicates the specific category or kind of military forces involved in or associated with an entity or event.
- 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_69d8278775fc8190b0802d22ca2f495d |
completed | April 9, 2026, 10:26 p.m. |
| NER | Named-entity recognition | batch_69de61b207cc8190b85b1ff0910b54da |
completed | April 14, 2026, 3:48 p.m. |
| PD | Predicate disambiguation | batch_69de05b8434c81908c33b1b513463b12 |
completed | April 14, 2026, 9:15 a.m. |
Created at: April 10, 2026, 12:59 a.m.