Triple
T36859541
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Whitworth screw thread system |
E910894
|
entity |
| Predicate | threadAngle |
P186591
|
FINISHED |
| Object | 55 degrees |
—
|
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: 55 degrees | Statement: [Whitworth screw thread system, threadAngle, 55 degrees]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: threadAngle Context triple: [Whitworth screw thread system, threadAngle, 55 degrees]
-
A.
leanAngle
Indicates the degree to which an entity is tilted or inclined away from a reference upright position.
-
B.
keyAngle
Indicates the angular orientation or rotation of a key relative to a reference position or axis.
-
C.
hasWireAngle
Indicates that one entity has a wire oriented or positioned at a specific angle relative to another reference or component.
-
D.
supportsAngleModes
Indicates that one entity provides functionality for handling or operating in multiple angle measurement modes (such as degrees, radians, or gradians) for another entity or context.
-
E.
bendAngle
Indicates the degree to which one part is bent relative to another, typically measured as the angle formed at their joint or intersection.
- 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_69f9fe1a1ca4819084c196f0041f0be2 |
completed | May 5, 2026, 2:26 p.m. |
| PD | Predicate disambiguation | batch_69f7cf7890008190a8bc355ff2d61c86 |
completed | May 3, 2026, 10:43 p.m. |
| PDg | Predicate description generation | batch_69f9fd66eed48190bdc26a8def328c2d |
completed | May 5, 2026, 2:23 p.m. |
Created at: May 3, 2026, 4:13 p.m.