Triple
T28281774
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Sasebo Heavy Industries |
E713168
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | heavy engineering company |
C136
|
CONCEPT FINISHED |
How this triple was built (1 step)
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.
CD
Concept disambiguation
gpt-5-mini-2025-08-07
Target class: heavy engineering company Context triple: [Sasebo Heavy Industries, instanceOf, heavy engineering company]
-
A.
heavy equipment manufacturer
A heavy equipment manufacturer is a company that designs, engineers, and produces large-scale machinery and vehicles used in construction, mining, agriculture, and other industrial applications.
-
B.
manufacturing company
chosen
A manufacturing company is an organization that transforms raw materials or components into finished goods through industrial processes, machinery, and labor for sale to other businesses or consumers.
-
C.
commercial vehicle manufacturer
A commercial vehicle manufacturer is a company that designs, produces, and sells vehicles intended primarily for business use, such as trucks, buses, and vans, to transport goods or passengers.
-
D.
industrial holding company
An industrial holding company is a parent corporation that owns controlling interests in multiple industrial or manufacturing businesses, managing them strategically while typically leaving day-to-day operations to subsidiary management.
-
E.
rolling stock maintenance company
A rolling stock maintenance company is an organization that inspects, services, repairs, and overhauls railway vehicles such as locomotives, passenger coaches, and freight wagons to ensure their safety, reliability, and regulatory compliance.
- F. None of above.
Provenance (1 batch)
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_69efb52275788190ae5181ccebef18ce |
completed | April 27, 2026, 7:12 p.m. |
Created at: April 27, 2026, 11:23 p.m.