Triple
T3634792
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Mk 82 bomb |
E77040
|
entity |
| Predicate | mountingStandard |
P2519
|
FINISHED |
| Object | 14-inch suspension lugs |
—
|
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: 14-inch suspension lugs | Statement: [Mk 82 bomb, mountingStandard, 14-inch suspension lugs]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: mountingStandard Context triple: [Mk 82 bomb, mountingStandard, 14-inch suspension lugs]
-
A.
mountingLocation
Indicates the physical position or surface on which something is attached, fixed, or installed.
-
B.
mountType
chosen
Indicates the manner or configuration in which one object is mounted or attached to another.
-
C.
baseStandard
Indicates that one entity serves as the foundational or reference standard upon which another entity is defined, measured, or evaluated.
-
D.
mountOption
Indicates that a particular configuration option is applied when mounting a filesystem, device, or resource.
-
E.
guardMounting
Indicates the action of assigning or taking up a position for guard duty, typically as part of a scheduled security or watch rotation.
- 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_69ad85dd0be48190b738990cb20c4731 |
completed | March 8, 2026, 2:21 p.m. |
| NER | Named-entity recognition | batch_69adc30594588190856694d4222c90d8 |
completed | March 8, 2026, 6:42 p.m. |
| PD | Predicate disambiguation | batch_69adb842be7c8190b7dfdb7c906f294c |
completed | March 8, 2026, 5:56 p.m. |
Created at: March 8, 2026, 3:24 p.m.