Triple
T22503479
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | SOLIDWORKS |
E556333
|
entity |
| Predicate | supportsModelingType |
P19966
|
FINISHED |
| Object | solid modeling |
—
|
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: solid modeling | Statement: [SOLIDWORKS, supportsModelingType, solid modeling]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: supportsModelingType Context triple: [SOLIDWORKS, supportsModelingType, solid modeling]
-
A.
supportsModelingOf
Indicates that one entity provides the capability or functionality needed to represent, simulate, or model another entity or process.
-
B.
supportsModelType
chosen
Indicates that an entity is compatible with, or can operate using, a specified model type.
-
C.
supportedModel
Indicates that one entity provides compatibility with, or operational backing for, a particular model.
-
D.
supportsContributionModel
Indicates that one entity enables or is compatible with a particular model or framework for making contributions (such as donations, content, or resources).
-
E.
supportsType
Indicates that one entity is capable of handling, accepting, or being compatible with a specified type.
- 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_69e11e555edc81909ca803587dafd747 |
completed | April 16, 2026, 5:37 p.m. |
| NER | Named-entity recognition | batch_69f15d5a01888190ba65a05616b63cbe |
completed | April 29, 2026, 1:22 a.m. |
| PD | Predicate disambiguation | batch_69e898be31448190be5ae7f5656f0497 |
completed | April 22, 2026, 9:45 a.m. |
Created at: April 16, 2026, 8:50 p.m.