Triple
T37291557
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Maynard tape primer system |
E925676
|
entity |
| Predicate | locatedInMechanism |
P40
|
FINISHED |
| Object | lock plate of the firearm |
—
|
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: lock plate of the firearm | Statement: [Maynard tape primer system, locatedInMechanism, lock plate of the firearm]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: locatedInMechanism Context triple: [Maynard tape primer system, locatedInMechanism, lock plate of the firearm]
-
A.
locatedIn
chosen
Indicates that one entity exists or is situated within the spatial, administrative, or conceptual boundaries of another entity.
-
B.
locatedOnStructureType
Indicates that an entity is situated on or supported by a particular type of structure.
-
C.
sometimesLocatedIn
Indicates that an entity is located in a given place only at certain times or under certain conditions, rather than permanently or always.
-
D.
locatedOnBody
Indicates that one entity is physically situated on the surface or external part of another entity’s body.
-
E.
locationInCableAssembly
Indicates a relationship where an element is positioned or situated within a specific cable assembly.
- 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_69f76eb0f86c819098dee07393e69ec3 |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_6a037c8efcd4819088c2aeead65d93df |
completed | May 12, 2026, 7:16 p.m. |
| PD | Predicate disambiguation | batch_6a037a11efc08190bb7cacc1325b4dc6 |
completed | May 12, 2026, 7:05 p.m. |
Created at: May 3, 2026, 4:16 p.m.