Triple
T32766383
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | SP5 (civilian variant) |
E837912
|
entity |
| Predicate | sharesErgonomicsWith |
P200166
|
FINISHED |
| Object | Heckler & Koch MP5 |
—
|
NE NERFINISHED |
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: Heckler & Koch MP5 | Statement: [SP5 (civilian variant), sharesErgonomicsWith, Heckler & Koch MP5]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: sharesErgonomicsWith Context triple: [SP5 (civilian variant), sharesErgonomicsWith, Heckler & Koch MP5]
-
A.
hasErgonomicType
Indicates that an object or product is associated with a specific ergonomic classification or design type.
-
B.
ergonomicRequirement
Indicates that one entity specifies or imposes ergonomic conditions, standards, or constraints that another entity must satisfy.
-
C.
sharesWorkWith
Indicates that one entity collaborates or participates jointly in work or tasks with another entity.
-
D.
sharesMantleWith
Indicates that two entities occupy or are associated with the same mantle, layer, or mantle-like structure.
-
E.
sharesApproachWith
Indicates that two entities use or follow the same or a very similar method, strategy, or way of doing something.
- F. None of above. chosen
Provenance (4 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_69f34939857c8190aa9970c51feec1eb |
completed | April 30, 2026, 12:21 p.m. |
| NER | Named-entity recognition | batch_69ff795d25d08190b7584c72be39d309 |
completed | May 9, 2026, 6:13 p.m. |
| PD | Predicate disambiguation | batch_69ff78a90fbc8190a62c57456dc1d4ad |
completed | May 9, 2026, 6:10 p.m. |
| PDg | Predicate description generation | batch_69ff795c702c8190b00844407f2882af |
completed | May 9, 2026, 6:13 p.m. |
Created at: May 1, 2026, 1:13 a.m.