Triple
T36859555
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Whitworth screw thread system |
E910894
|
entity |
| Predicate | threadSeries |
P76458
|
FINISHED |
| Object | 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: coarse thread series | Statement: [Whitworth screw thread system, threadSeries, coarse thread series]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: threadSeries Context triple: [Whitworth screw thread system, threadSeries, coarse thread series]
-
A.
seriesWith
Indicates that one entity is part of, or grouped together in, the same series or sequence as another entity.
-
B.
seriesOf
chosen
Indicates that one entity is a sequence or ordered set of related items, events, or parts that collectively form or belong to another entity.
-
C.
threadType
Indicates the classification or category of a thread based on its purpose, content, or communication style.
-
D.
isSeriesOf
Indicates that one entity is a sequence or set of related items that collectively form a series associated with another entity.
-
E.
threadBehavior
Indicates how a thread operates or responds under certain conditions within a concurrent or multi-threaded context.
- 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_69fb563aec448190875410fb1a3ed624 |
completed | May 6, 2026, 2:54 p.m. |
| PD | Predicate disambiguation | batch_69fb35b9ede881908aaae93a215525df |
completed | May 6, 2026, 12:36 p.m. |
Created at: May 3, 2026, 4:13 p.m.