Triple
T8982098
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | HK433 |
E214554
|
entity |
| Predicate | chargingHandle |
P86159
|
FINISHED |
| Object | non-reciprocating charging handle |
—
|
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: non-reciprocating charging handle | Statement: [HK433, chargingHandle, non-reciprocating charging handle]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: chargingHandle Context triple: [HK433, chargingHandle, non-reciprocating charging handle]
-
A.
chargingPortType
Indicates the specific kind of connector or interface used for charging a device.
-
B.
charging
Indicates that one entity is supplying electrical energy to another entity’s battery or power storage system.
-
C.
requiresCharging
Indicates that an entity depends on being recharged (e.g., with electrical power or energy) in order to function or continue operating.
-
D.
chargingPortLocation
Indicates the physical position or area on an object or device where its charging port is located.
-
E.
chargingLocation
Indicates the place or facility where an entity is being or can be charged (e.g., electrically powered or re-energized).
- 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_69ca839ea8b88190922c6a326ffcc0d3 |
completed | March 30, 2026, 2:07 p.m. |
| NER | Named-entity recognition | batch_69cc67a891e881909e4b84ed82491651 |
completed | April 1, 2026, 12:32 a.m. |
| PD | Predicate disambiguation | batch_69cc5edba0f88190b97401636a076d7a |
completed | March 31, 2026, 11:55 p.m. |
| PDg | Predicate description generation | batch_69cc5febd0a08190b2de6fb422343001 |
completed | March 31, 2026, 11:59 p.m. |
Created at: March 30, 2026, 7:03 p.m.