Triple
T28627696
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | German Wikiversity |
E724565
|
entity |
| Predicate | allowsOriginalResearch |
P178296
|
FINISHED |
| Object | yes |
—
|
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: yes | Statement: [German Wikiversity, allowsOriginalResearch, yes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: allowsOriginalResearch Context triple: [German Wikiversity, allowsOriginalResearch, yes]
-
A.
originallyResearchedFor
Indicates that something was first investigated, developed, or studied with a particular initial purpose, target, or application in mind.
-
B.
usedResearchFrom
Indicates that one entity based its work, findings, or outputs on research conducted or provided by another entity.
-
C.
hasResearchUse
Indicates that an entity is used for, or associated with, conducting research activities or purposes.
-
D.
supportsResearchIn
Indicates that one entity provides resources, assistance, or infrastructure that enables or advances research activities in a particular field or area for another entity.
-
E.
supportedResearch
Indicates that one entity provided assistance, resources, or backing to enable or advance the research activities of another entity.
- F. None of above. chosen
Provenance (4 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_69f01d822ac08190932de59ec2268ed2 |
completed | April 28, 2026, 2:37 a.m. |
| NER | Named-entity recognition | batch_69f70e8755a48190931eaa77946f9460 |
completed | May 3, 2026, 8:59 a.m. |
| PD | Predicate disambiguation | batch_69f70abc00848190a1c3f495ef6c8dc6 |
completed | May 3, 2026, 8:43 a.m. |
| PDg | Predicate description generation | batch_69f70e854b9c8190a3416e2189e17742 |
completed | May 3, 2026, 8:59 a.m. |
Created at: April 28, 2026, 4:36 a.m.