Triple
T3739868
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Type 1 AC connector |
E79671
|
entity |
| Predicate | mechanicalLocking |
P34001
|
FINISHED |
| Object | latching mechanism on plug |
—
|
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: latching mechanism on plug | Statement: [Type 1 AC connector, mechanicalLocking, latching mechanism on plug]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: mechanicalLocking Context triple: [Type 1 AC connector, mechanicalLocking, latching mechanism on plug]
-
A.
mechanicalKeying
Indicates that one entity physically engages or interlocks with another through a shaped mechanical interface (such as keys, slots, or profiles) to ensure correct positioning, alignment, or coupling.
-
B.
lockType
chosen
Indicates the specific kind or category of locking mechanism or access restriction applied to an entity or resource.
-
C.
openingMechanism
Indicates the method or mechanism by which an object or structure is opened or made accessible.
-
D.
lockSystemSupplied
Indicates that a system-provided locking mechanism is used to control access or state, rather than a custom or user-defined lock.
-
E.
hasMechanism
Indicates that one entity operates, functions, or produces an effect through the specified mechanism or process.
- 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_69ad8b115610819095b02007da5ca3cb |
completed | March 8, 2026, 2:43 p.m. |
| NER | Named-entity recognition | batch_69adcb5344fc8190b183aca5c04e3bcc |
completed | March 8, 2026, 7:17 p.m. |
| PD | Predicate disambiguation | batch_69adc048f28c819092bed16a95a3cac1 |
completed | March 8, 2026, 6:30 p.m. |
Created at: March 8, 2026, 3:34 p.m.