Triple
T6349867
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Consorcio Regional de Transportes de Madrid |
E142841
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | public consortium |
C20234
|
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: public consortium Context triple: [Consorcio Regional de Transportes de Madrid, instanceOf, public consortium]
-
A.
private consortium
A private consortium is a collaborative alliance of independent, typically private-sector organizations that pool resources, expertise, and decision-making authority to pursue shared objectives while remaining legally distinct entities.
-
B.
business consortium
A business consortium is a collaborative association of independent companies that pool resources, expertise, or capital to pursue shared objectives, projects, or market opportunities while retaining their individual autonomy.
-
C.
multinational consortium
A multinational consortium is a collaborative alliance of independent organizations from multiple countries that pool resources, expertise, and risks to pursue shared objectives or large-scale projects.
-
D.
private investment consortium
A private investment consortium is a group of non-public investors who pool capital and expertise to jointly finance, manage, and profit from selected investment opportunities.
-
E.
trading consortium
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.
- F. None of above. chosen
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_69c008d6dcbc8190aa1c2f1fd8916b42 |
completed | March 22, 2026, 3:20 p.m. |
Created at: March 22, 2026, 4:31 p.m.