Triple
T649715
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Mauser BK-27 |
E11318
|
entity |
| Predicate | mounting |
P2519
|
FINISHED |
| Object | internal gun installation |
—
|
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: internal gun installation | Statement: [Mauser BK-27, mounting, internal gun installation]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: mounting Context triple: [Mauser BK-27, mounting, internal gun installation]
-
A.
mountType
chosen
Indicates the manner or configuration in which one object is mounted or attached to another.
-
B.
mapped
Indicates that one entity has been associated, corresponded, or linked systematically to another according to some defined mapping or alignment.
-
C.
holding
Indicates that one entity is physically grasping, carrying, or keeping another entity in its possession or control.
-
D.
suspension
Indicates the temporary removal or halting of a privilege, activity, or status for an entity, often as a consequence or precaution.
-
E.
backing
Indicates providing support, endorsement, or financial/resources assistance to someone or something, often enabling or strengthening their actions or position.
- 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_69a493266a2881909daf4c40f719dee8 |
completed | March 1, 2026, 7:27 p.m. |
| NER | Named-entity recognition | batch_69a49f31e70c81909a2ac1d939f7ec07 |
completed | March 1, 2026, 8:18 p.m. |
| PD | Predicate disambiguation | batch_69a49d0eade081909c47e85ed55f808d |
completed | March 1, 2026, 8:09 p.m. |
Created at: March 1, 2026, 7:36 p.m.