Triple
T1692623
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Lockheed P-38 Lightning |
E36582
|
entity |
| Predicate | armamentExternal |
P22939
|
FINISHED |
| Object | bombs |
—
|
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: bombs | Statement: [Lockheed P-38 Lightning, armamentExternal, bombs]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: armamentExternal Context triple: [Lockheed P-38 Lightning, armamentExternal, bombs]
-
A.
militaryUse
Indicates the use of something (such as land, facilities, equipment, or resources) for military purposes or operations.
-
B.
secondaryArmament
Indicates that one entity serves as a secondary or auxiliary weapon system associated with another primary platform or armament.
-
C.
primaryArmament
Indicates the main weapon or principal offensive system that an entity (such as a vehicle, vessel, or platform) is equipped with or uses.
-
D.
armamentStations
chosen
Indicates a relationship where specific locations or mounts on a platform (such as a vehicle, vessel, or structure) are designated for installing or carrying weapons or armaments.
-
E.
armedVariants
Indicates that one entity is a version or model of another that is equipped with weapons or enhanced armaments.
- 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_69a886151508819084fa7f1ce6e05577 |
completed | March 4, 2026, 7:20 p.m. |
| NER | Named-entity recognition | batch_69aaf3359ce48190803b322db8ad6027 |
completed | March 6, 2026, 3:31 p.m. |
| PD | Predicate disambiguation | batch_69aa61b71cec8190b273588051058ebd |
completed | March 6, 2026, 5:10 a.m. |
Created at: March 4, 2026, 7:29 p.m.