Triple
T36805132
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Dubna State University |
E909427
|
entity |
| Predicate | hasCollaborationField |
P190039
|
FINISHED |
| Object | nuclear research |
—
|
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: nuclear research | Statement: [Dubna State University, hasCollaborationField, nuclear research]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasCollaborationField Context triple: [Dubna State University, hasCollaborationField, nuclear research]
-
A.
hasCollaborationIn
Indicates that two or more entities work together or jointly participate in a specific project, context, or domain.
-
B.
containsCollaboration
Indicates that one entity includes or involves a collaborative relationship or joint activity with another entity.
-
C.
hasCollaborationDomain
chosen
Indicates that two or more entities work together within a specified field, area, or domain of collaboration.
-
D.
isCollaboration
Indicates that two or more entities are jointly working together toward a shared goal or producing something in partnership.
-
E.
hasSiblingCollaboration
Indicates a collaborative relationship between two entities that are considered siblings within the same hierarchy or family.
- 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_69f76e7cbbf48190891227b14d041139 |
completed | May 3, 2026, 3:49 p.m. |
| NER | Named-entity recognition | batch_6a037c8e2c648190a65fc9c7872861af |
completed | May 12, 2026, 7:16 p.m. |
| PD | Predicate disambiguation | batch_6a037a0e039481908a4a2666f76c5363 |
completed | May 12, 2026, 7:05 p.m. |
Created at: May 3, 2026, 4:12 p.m.