Triple
T7199177
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | ICCFD Senior Award |
E168693
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | computational fluid dynamics award |
C16
|
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: computational fluid dynamics award Context triple: [ICCFD Senior Award, instanceOf, computational fluid dynamics award]
-
A.
distributed computing award
A distributed computing award is a formal recognition given to individuals, teams, or organizations for outstanding contributions, innovations, or achievements in the theory, design, or practical deployment of distributed computing systems.
-
B.
science and technology award
chosen
A science and technology award is a formal recognition given to individuals or organizations for outstanding achievements, innovations, or contributions in scientific research and technological development.
-
C.
professional society award
A professional society award is a formal recognition given by an organized professional association to honor outstanding achievements, contributions, or service within a specific field or discipline.
-
D.
computing honor
Computing honor is the ethical principle of using digital technologies with integrity, respect, and responsibility toward others and society.
-
E.
program of the American Society of Mechanical Engineers
A program of the American Society of Mechanical Engineers is an organized set of activities, initiatives, or services designed to advance mechanical engineering knowledge, practice, standards, and professional development for its members and the broader engineering community.
- 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_69c68a5376748190bb500f03df86e93e |
completed | March 27, 2026, 1:46 p.m. |
Created at: March 27, 2026, 2:52 p.m.