Triple
T11909866
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Underground Group |
E283364
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | engineering and design organization |
C426
|
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: engineering and design organization Context triple: [Underground Group, instanceOf, engineering and design organization]
-
A.
systems engineering organization
A systems engineering organization is a structured group that plans, designs, integrates, and manages complex systems across their life cycles to meet stakeholder needs within technical, cost, and schedule constraints.
-
B.
software engineering organization
A software engineering organization is a structured group of people, processes, and tools dedicated to designing, building, testing, deploying, and maintaining software systems to meet specific business or user needs.
-
C.
engineering division
The engineering division is an organizational unit responsible for designing, developing, and maintaining technical systems, products, and infrastructure within a company or institution.
-
D.
technology and design center
A technology and design center is a collaborative hub where people access tools, expertise, and resources to research, prototype, and develop innovative technological and design solutions.
-
E.
engineering firm
chosen
An engineering firm is a business organization that provides professional engineering services—such as design, analysis, consulting, and project management—to plan, develop, and implement technical solutions for clients in various industries.
- 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_69d6ab2c07e88190ba13b0d21fd6cf33 |
completed | April 8, 2026, 7:23 p.m. |
Created at: April 8, 2026, 9:44 p.m.