Triple
T32493873
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Toulouse Tech |
E830463
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | engineering and technology consortium |
C343
|
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 technology consortium Context triple: [Toulouse Tech, instanceOf, engineering and technology consortium]
-
A.
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.
-
B.
research consortium
chosen
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.
-
C.
engineering institute
An engineering institute is an educational and research organization dedicated to teaching, advancing, and applying engineering principles and technologies across various specialized fields.
-
D.
architectural and engineering institute
An architectural and engineering institute is an educational and research institution dedicated to training professionals and advancing knowledge in the fields of architecture, civil engineering, and related built-environment disciplines.
-
E.
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.
- 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_69f34920aa4081908d8fb0277414b911 |
completed | April 30, 2026, 12:20 p.m. |
Created at: May 1, 2026, 12:59 a.m.