Triple
T35048174
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Syktyvkar State University |
E1011258
|
entity |
| Predicate | hasResearchFocusRegion |
P37341
|
FINISHED |
| Object | Komi Republic |
E692099
|
NE 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: Komi Republic | Statement: [Syktyvkar State University, hasResearchFocusRegion, Komi Republic]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasResearchFocusRegion Context triple: [Syktyvkar State University, hasResearchFocusRegion, Komi Republic]
-
A.
studiesRegion
chosen
Indicates that an entity engages in the academic or systematic study of a particular geographic or cultural region.
-
B.
regionOfAcademicFocus
Indicates the academic subject area or discipline that an entity (such as a person or program) primarily concentrates on or specializes in.
-
C.
studiedInRegion
Indicates that an entity pursued studies or received education within a specified geographic region.
-
D.
hasResearchArea
Indicates that an entity (such as a person, project, or organization) is associated with or focused on a particular field or area of research.
-
E.
regionOfStudy
Indicates the academic or research area that is the focus of someone’s study or investigation.
- F. None of above.
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_69f76dcfdda48190b1ebae5da8b54f12 |
completed | May 3, 2026, 3:46 p.m. |
| NER | Named-entity recognition | batch_6a037c8c34f88190ace26f555827f23e |
completed | May 12, 2026, 7:16 p.m. |
| NED1 | Entity disambiguation (via context triple) | batch_6a38369913e081909784a08500a0f9f3 |
completed | June 21, 2026, 7:08 p.m. |
| PD | Predicate disambiguation | batch_6a037a016960819093ed4990fb4d9d36 |
completed | May 12, 2026, 7:05 p.m. |
Created at: May 3, 2026, 4:01 p.m.