Triple
T1833514
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Leibniz University Hannover |
E41010
|
entity |
| Predicate | focusesOnResearch |
P24329
|
FINISHED |
| Object | engineering sciences |
—
|
LITERAL FINISHED |
How this triple was built (2 steps)
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.
NER
Named-entity recognition
gpt-5-mini
Instruction
Given a phrase, classify it is english named entity (e.g., persons, organizations, works of art) in Latin script, or not (e.g., literals, dates, URLs, verbose phrases). For disambiguation, the statement where the phrase occurs as object is also given. Please return a JSON object with `phrase` (string, the phrase being analyzed) and `is_ne` (boolean, indicating whether the phrase is a Named Entity).
Input
Phrase: engineering sciences | Statement: [Leibniz University Hannover, focusesOnResearch, engineering sciences]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: focusesOnResearch Context triple: [Leibniz University Hannover, focusesOnResearch, engineering sciences]
-
A.
researchTopic
chosen
Indicates that a subject conducts or focuses research on a particular topic or area of study.
-
B.
usesResearchSubject
Indicates that one entity employs or utilizes another entity as a research subject in a study or investigation.
-
C.
conductsResearchAt
Indicates that a subject carries out research activities at a specified institution, organization, or location.
-
D.
focusesOn
Indicates that one entity directs its attention, effort, or primary activity toward another entity or specific subject.
-
E.
academicFocus
Indicates the primary field of study, discipline, or subject area that an entity concentrates on academically.
- F. None of above.
Provenance (3 batches)
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_69a88647f9388190909bc36e795bdaec |
completed | March 4, 2026, 7:21 p.m. |
| NER | Named-entity recognition | batch_69abb32d35508190bf1c487dffbecaf0 |
completed | March 7, 2026, 5:10 a.m. |
| PD | Predicate disambiguation | batch_69abafd88ebc81908208394746351fe6 |
completed | March 7, 2026, 4:55 a.m. |
Created at: March 4, 2026, 7:33 p.m.