Triple
T8137728
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Iron and Steel Corporation of Great Britain |
E190013
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | nationalized industry body |
C19246
|
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: nationalized industry body Context triple: [Iron and Steel Corporation of Great Britain, instanceOf, nationalized industry body]
-
A.
railway industry body
A railway industry body is an organization that represents, coordinates, and sets standards or policies for companies and stakeholders involved in the rail transport sector.
-
B.
federally owned corporation
A federally owned corporation is a government-established legal entity that operates commercial or public service activities on behalf of the federal government while retaining a distinct corporate structure.
-
C.
nuclear industry company
A nuclear industry company is an organization that designs, builds, operates, or services nuclear facilities and technologies for energy production, research, medicine, or defense while managing strict safety, regulatory, and environmental requirements.
-
D.
government-backed organization
chosen
A government-backed organization is an entity that operates with financial support, authorization, or guarantees from a government to carry out specific public, economic, or policy-related functions.
-
E.
public administration body
A public administration body is an organization within the public sector responsible for implementing laws, delivering public services, and managing governmental policies and resources on behalf of the state and its citizens.
- 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_69ca82bd9900819099477cdc2eb4244f |
completed | March 30, 2026, 2:03 p.m. |
Created at: March 30, 2026, 5:35 p.m.