Triple
T36859640
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Whitworth standard screw thread |
E910896
|
entity |
| Predicate | hasCoarseSeries |
P35499
|
FINISHED |
| Object | BSW coarse thread series |
—
|
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: BSW coarse thread series | Statement: [Whitworth standard screw thread, hasCoarseSeries, BSW coarse thread series]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasCoarseSeries Context triple: [Whitworth standard screw thread, hasCoarseSeries, BSW coarse thread series]
-
A.
hasSubSeries
chosen
Indicates that one series is a subordinate or component series within a larger parent series.
-
B.
hasSeriesStructure
Indicates that one entity is organized as a sequence or series of related components or parts.
-
C.
hasScaleSeries
Indicates that one entity is associated with a particular ordered set or sequence of scales used for measurement, evaluation, or representation.
-
D.
hasStandardSeries
Indicates that an entity is associated with, or belongs to, a designated standard series or standardized sequence.
-
E.
hasParentSeries
Indicates that a work or item belongs to, or is derived from, a broader parent series.
- 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_69f76e8033d48190a59274f86f13be48 |
completed | May 3, 2026, 3:49 p.m. |
| NER | Named-entity recognition | batch_6a037c8e2c648190a65fc9c7872861af |
completed | May 12, 2026, 7:16 p.m. |
| PD | Predicate disambiguation | batch_6a037a0e039481908a4a2666f76c5363 |
completed | May 12, 2026, 7:05 p.m. |
Created at: May 3, 2026, 4:13 p.m.