Triple
T24824632
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | European XFEL |
E621154
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | large-scale research infrastructure |
C44349
|
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: large-scale research infrastructure Context triple: [European XFEL, instanceOf, large-scale research infrastructure]
-
A.
scientific infrastructure project
chosen
A scientific infrastructure project is a large-scale, coordinated effort to design, build, and maintain shared facilities, platforms, or systems that enable and support long-term scientific research and innovation.
-
B.
research infrastructure collection
A research infrastructure collection is an organized set of facilities, equipment, data, and services that together support and enable systematic scientific investigation and innovation.
-
C.
research infrastructure component
A research infrastructure component is a foundational hardware, software, or service element that supports the collection, storage, processing, and sharing of data and tools necessary for conducting and advancing research.
-
D.
research facility
A research facility is a specialized institution equipped with laboratories, instruments, and resources where scientists and experts systematically investigate, experiment, and develop new knowledge or technologies.
-
E.
public research institution
A public research institution is a government-funded organization dedicated to advancing knowledge and innovation through systematic investigation, experimentation, and dissemination of findings for the benefit of society.
- 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_69e2fac0c3b881909110e5a56c6fa46f |
completed | April 18, 2026, 3:30 a.m. |
Created at: April 18, 2026, 5:05 a.m.