Triple
T18299253
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Scottish universities |
E438310
|
entity |
| Predicate | researchStrengths |
P366
|
FINISHED |
| Object | science and engineering |
—
|
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: science and engineering | Statement: [Scottish universities, researchStrengths, science and engineering]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: researchStrengths Context triple: [Scottish universities, researchStrengths, science and engineering]
-
A.
researchStrength
chosen
Indicates the degree to which an entity possesses strong capabilities, performance, or impact in conducting research.
-
B.
researchFocusSince
Indicates the point in time since which an entity has maintained a particular research focus or area of study.
-
C.
researchTopic
Indicates that a subject conducts or focuses research on a particular topic or area of study.
-
D.
researchValue
Indicates that something is considered useful, important, or relevant for research or scholarly investigation.
-
E.
researchBaseOf
Indicates that one entity serves as the primary location, facility, or site from which another entity conducts or supports its research activities.
- 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_69d8b915e3e881909125d760c15d0c29 |
completed | April 10, 2026, 8:47 a.m. |
| NER | Named-entity recognition | batch_69e5017d96588190ac1e326803142976 |
completed | April 19, 2026, 4:23 p.m. |
| PD | Predicate disambiguation | batch_69e44fdf43d08190bbcfb6b1fe3cc0ee |
completed | April 19, 2026, 3:45 a.m. |
Created at: April 10, 2026, 10:35 a.m.