Triple
T17355961
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | M1C sniper variant |
E421934
|
entity |
| Predicate | mountAttachmentMethod |
P42077
|
FINISHED |
| Object | receiver side-mounted base |
—
|
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: receiver side-mounted base | Statement: [M1C sniper variant, mountAttachmentMethod, receiver side-mounted base]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: mountAttachmentMethod Context triple: [M1C sniper variant, mountAttachmentMethod, receiver side-mounted base]
-
A.
mountType
Indicates the manner or configuration in which one object is mounted or attached to another.
-
B.
attachedTo
Indicates that one entity is physically or logically fastened, connected, or joined to another entity.
-
C.
mountOption
Indicates that a particular configuration option is applied when mounting a filesystem, device, or resource.
-
D.
mountingInterface
Indicates that one entity serves as the surface, structure, or connection point onto which another entity is mounted or attached.
-
E.
attachmentMethod
chosen
Indicates the way or technique by which one entity is fastened, joined, or secured to another.
- 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_69d889d520008190a26917a95bf1c2ea |
completed | April 10, 2026, 5:25 a.m. |
| NER | Named-entity recognition | batch_69e43a487bd8819081c6d1e4aa466d6f |
completed | April 19, 2026, 2:13 a.m. |
| PD | Predicate disambiguation | batch_69e3b02662d08190a07d0fb5c04b6f33 |
completed | April 18, 2026, 4:24 p.m. |
Created at: April 10, 2026, 5:44 a.m.