Triple
T32608776
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Honorary Doctorate of Engineering from Technische Hochschule Stuttgart |
E833596
|
entity |
| Predicate | instanceOf |
P0
|
FINISHED |
| Object | honorary academic degree |
C25130
|
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: honorary academic degree Context triple: [Honorary Doctorate of Engineering from Technische Hochschule Stuttgart, instanceOf, honorary academic degree]
-
A.
Honorary degree
chosen
An honorary degree is an academic distinction awarded by a university to individuals in recognition of their outstanding achievements or contributions, without the usual requirements of coursework or examinations.
-
B.
honorary status
Honorary status is a formally recognized, typically non-remunerative distinction granted to an individual as a mark of respect, achievement, or contribution, without conferring the full rights or responsibilities of a regular position.
-
C.
university honor
A university honor is a formal recognition awarded by an academic institution to acknowledge exceptional achievement, merit, or contribution in scholarly, extracurricular, or service domains.
-
D.
honorary order
An honorary order is a formal system of titles, decorations, or memberships conferred by a state or organization to recognize individuals for distinguished service, achievement, or merit.
-
E.
honorary membership grade
An honorary membership grade is a special, typically non-voting class of membership conferred by an organization to recognize individuals for distinguished service, achievement, or contribution without requiring them to meet standard membership criteria.
- 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_69f3492bfa648190b6ae472074634e29 |
completed | April 30, 2026, 12:21 p.m. |
Created at: May 1, 2026, 1:05 a.m.