Triple
T649643
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Euroradar |
E11316
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | industrial consortium |
C1906
|
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: industrial consortium Context triple: [Euroradar, instanceOf, industrial consortium]
-
A.
research consortium
A research consortium is a collaborative alliance of multiple organizations or institutions that pool resources, expertise, and infrastructure to conduct joint research toward shared scientific or technological goals.
-
B.
business cartel
A business cartel is a group of independent companies that secretly or explicitly collude to control prices, limit competition, or manipulate markets for mutual benefit.
-
C.
trading consortium
chosen
A trading consortium is a collaborative alliance of independent businesses or organizations that pool resources, share information, and coordinate strategies to enhance their collective trading power and market reach.
-
D.
manufacturing company
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.
-
E.
industrial conflict
Industrial conflict is a state of disagreement and opposition between employers and employees (or their representatives) over work-related issues such as wages, conditions, rights, and organizational control.
- 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_69a493266a2881909daf4c40f719dee8 |
completed | March 1, 2026, 7:27 p.m. |
Created at: March 1, 2026, 7:36 p.m.