Triple
T28310264
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | HK53 |
E713973
|
entity |
| Predicate | chargingHandleLocation |
P164262
|
FINISHED |
| Object | left side, forward |
—
|
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: left side, forward | Statement: [HK53, chargingHandleLocation, left side, forward]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: chargingHandleLocation Context triple: [HK53, chargingHandleLocation, left side, forward]
-
A.
chargingHandle
Indicates the component or action used to manually cycle or charge a firearm’s operating mechanism, typically to chamber a round or reset the bolt.
-
B.
chargingPortLocation
Indicates the physical position or area on an object or device where its charging port is located.
-
C.
chargingLocation
Indicates the place or facility where an entity is being or can be charged (e.g., electrically powered or re-energized).
-
D.
chargingPortType
Indicates the specific kind of connector or interface used for charging a device.
-
E.
chargingInterface
Indicates that one entity serves as a power/energy charging connection or port used by another entity.
- 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_69efb5256afc8190b9322d25c3ae6320 |
completed | April 27, 2026, 7:12 p.m. |
| NER | Named-entity recognition | batch_69f644e1e0b48190b48f3e7b5d408dbd |
completed | May 2, 2026, 6:39 p.m. |
| PD | Predicate disambiguation | batch_69f641e0fde08190bf06a1c5b388aa84 |
completed | May 2, 2026, 6:26 p.m. |
| PDg | Predicate description generation | batch_69f6430975b481909191219ad13ef77e |
completed | May 2, 2026, 6:31 p.m. |
Created at: April 27, 2026, 11:40 p.m.