Triple
T1915975
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Technical University of Berlin |
E40017
|
entity |
| Predicate | researchOrientation |
P366
|
FINISHED |
| Object | research-intensive |
—
|
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: research-intensive | Statement: [Technical University of Berlin, researchOrientation, research-intensive]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: researchOrientation Context triple: [Technical University of Berlin, researchOrientation, research-intensive]
-
A.
researchTopic
Indicates that a subject conducts or focuses research on a particular topic or area of study.
-
B.
researchStrength
chosen
Indicates the degree to which an entity possesses strong capabilities, performance, or impact in conducting research.
-
C.
researchUser
Indicates that an entity conducts research on, studies, or investigates a particular user.
-
D.
researchContext
Indicates the situational, methodological, or thematic setting within which a particular piece of research is conducted or interpreted.
-
E.
researchProgram
Indicates that an entity is engaged in, associated with, or part of a structured research initiative or program.
- 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_69a8864298748190a2f2fd34f7ef8d77 |
completed | March 4, 2026, 7:21 p.m. |
| NER | Named-entity recognition | batch_69abb1e517e8819086e4bf5a305aeb25 |
completed | March 7, 2026, 5:04 a.m. |
| PD | Predicate disambiguation | batch_69abafed2ab481908920334e77b1021b |
completed | March 7, 2026, 4:56 a.m. |
Created at: March 4, 2026, 7:35 p.m.