Triple
T37593879
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | MG 34 Panzerlauf |
E935327
|
entity |
| Predicate | hasMounting |
P34295
|
FINISHED |
| Object | coaxial mount |
—
|
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: coaxial mount | Statement: [MG 34 Panzerlauf, hasMounting, coaxial mount]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasMounting Context triple: [MG 34 Panzerlauf, hasMounting, coaxial mount]
-
A.
hasMount
Indicates that an entity is equipped with, riding, or otherwise using another entity as a mount for transportation or support.
-
B.
hasMountingStyle
Indicates the method or configuration by which one entity is physically attached, fixed, or mounted to another surface or structure.
-
C.
hasMountingFeature
chosen
Indicates that one entity includes or provides a structural feature intended for mounting or attaching another entity.
-
D.
guardMounting
Indicates the action of assigning or taking up a position for guard duty, typically as part of a scheduled security or watch rotation.
-
E.
mountingInterface
Indicates that one entity serves as the surface, structure, or connection point onto which another entity is mounted or attached.
- 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_69f76ecf39c081909baffe597bb55273 |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_69ff9bed58dc8190a204816d4ed6c32c |
completed | May 9, 2026, 8:41 p.m. |
| PD | Predicate disambiguation | batch_69ff9b69653c81908ab0d88055a66a88 |
completed | May 9, 2026, 8:39 p.m. |
Created at: May 3, 2026, 4:18 p.m.