Triple
T322488
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | RJ45 |
E6443
|
entity |
| Predicate | hasLatchingMechanism |
P8166
|
FINISHED |
| Object | plastic locking tab |
—
|
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: plastic locking tab | Statement: [RJ45, hasLatchingMechanism, plastic locking tab]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasLatchingMechanism Context triple: [RJ45, hasLatchingMechanism, plastic locking tab]
-
A.
hasMechanism
chosen
Indicates that one entity operates, functions, or produces an effect through the specified mechanism or process.
-
B.
reliabilityMechanism
Indicates a mechanism or process that ensures the dependable, consistent, and correct functioning of a system or relationship.
-
C.
hasChamber
Indicates that one entity possesses, contains, or is associated with a distinct enclosed space or compartment (a chamber).
-
D.
isMechanicalOrElectronic
Indicates that something operates using mechanical components, electronic components, or a combination of both.
-
E.
backedByMechanism
Indicates that something is supported, enabled, or made possible by an underlying mechanism or system.
- 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_69a2e7933d6c8190bb2592ad13286ef2 |
completed | Feb. 28, 2026, 1:03 p.m. |
| NER | Named-entity recognition | batch_69a2ea82ba748190bae651f5de908617 |
completed | Feb. 28, 2026, 1:15 p.m. |
| PD | Predicate disambiguation | batch_69a2e948048c819098ba4de9261ef2ef |
completed | Feb. 28, 2026, 1:10 p.m. |
Created at: Feb. 28, 2026, 1:08 p.m.