Triple
T36859533
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Whitworth screw thread system |
E910894
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | screw thread standard |
C62894
|
CONCEPT FINISHED |
How this triple was built (1 step)
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.
CD
Concept disambiguation
gpt-5-mini-2025-08-07
Target class: screw thread standard Context triple: [Whitworth screw thread system, instanceOf, screw thread standard]
-
A.
fastener standard
chosen
A fastener standard is a formal specification that defines the dimensions, materials, performance requirements, and testing methods for mechanical fasteners to ensure compatibility, safety, and interchangeability across applications.
-
B.
DIN standard
A DIN standard is a formal technical specification developed by the German Institute for Standardization (DIN) that defines uniform criteria, dimensions, methods, or quality requirements for products, processes, and services.
-
C.
piping standard
A piping standard is a formal specification that defines the materials, dimensions, design, fabrication, testing, and installation requirements for piping systems to ensure safety, compatibility, and performance.
-
D.
military standard
A military standard is an officially established set of technical, procedural, or quality requirements used by armed forces to ensure compatibility, reliability, and uniformity of equipment, systems, and practices.
-
E.
numerical control standard
A numerical control standard is a formal specification that defines the rules, formats, and protocols for programming and operating computer-controlled machine tools to ensure consistency, interoperability, and accuracy in automated manufacturing processes.
- F. None of above.
Provenance (1 batch)
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_69f76e8033d48190a59274f86f13be48 |
completed | May 3, 2026, 3:49 p.m. |
Created at: May 3, 2026, 4:13 p.m.