Triple
T36859544
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Whitworth screw thread system |
E910894
|
entity |
| Predicate | threadProfile |
P186725
|
FINISHED |
| Object | symmetrical V-thread |
—
|
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: symmetrical V-thread | Statement: [Whitworth screw thread system, threadProfile, symmetrical V-thread]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: threadProfile Context triple: [Whitworth screw thread system, threadProfile, symmetrical V-thread]
-
A.
timeProfile
Indicates the temporal pattern or schedule according to which an action, process, or relationship occurs or is distributed over time.
-
B.
threadCount
Indicates the number of concurrent threads associated with an entity, such as a process, task, or execution context.
-
C.
threadIdOutput
Indicates that an output is associated with, or originates from, a specific thread identified by a thread ID.
-
D.
threadType
Indicates the classification or category of a thread based on its purpose, content, or communication style.
-
E.
threadLocal
Indicates that a value or resource is specific to, and accessible only within, a single execution thread, separate from other threads.
- F. None of above. chosen
Provenance (4 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_69fa0a7b00948190a257273d9968c5d7 |
completed | May 5, 2026, 3:19 p.m. |
| PD | Predicate disambiguation | batch_69f9fec9c9488190ae2a349651a02782 |
completed | May 5, 2026, 2:29 p.m. |
| PDg | Predicate description generation | batch_69fa0a799b9081909bfa8293a22c4b00 |
completed | May 5, 2026, 3:19 p.m. |
Created at: May 3, 2026, 4:13 p.m.