Triple
T22503509
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | SOLIDWORKS |
E556333
|
entity |
| Predicate | supportsFileFormat |
P8463
|
FINISHED |
| Object | IGES |
—
|
NE NERFINISHED |
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: IGES | Statement: [SOLIDWORKS, supportsFileFormat, IGES]
NED1
Entity disambiguation (via context triple)
gpt-5-mini-2025-08-07
Target entity: IGES Context triple: [SOLIDWORKS, supportsFileFormat, IGES]
-
A.
IGES
chosen
IGES is a widely used neutral file format standard for exchanging 2D and 3D CAD data between different computer-aided design systems.
-
B.
Parasolid
Parasolid is a widely used geometric modeling kernel developed by Siemens that underpins 3D CAD, CAM, and CAE applications by providing robust solid and surface modeling capabilities.
-
C.
IGS
IGS is a global scientific organization that provides high-precision GNSS data and products to support geodesy, Earth science, and positioning applications.
-
D.
IGS
IGS is the IATA airport code assigned to Neuburg Air Base in Germany.
-
E.
EGNX
EGNX is the ICAO airport code for East Midlands Airport, a major passenger and cargo hub in central England.
- F. None of above.
- G. Unsure - the case is ambiguous/there is not enough information to decide.
Provenance (2 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. |
Created at: April 16, 2026, 8:50 p.m.