Triple
T33974872
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | RHINE |
E871107
|
entity |
| Predicate | hasStudyDesign |
P98380
|
FINISHED |
| Object | multicenter |
—
|
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: multicenter | Statement: [RHINE, hasStudyDesign, multicenter]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasStudyDesign Context triple: [RHINE, hasStudyDesign, multicenter]
-
A.
studyDesign
chosen
Indicates the type or structure of the research methodology or experimental setup used in a study.
-
B.
hasScientificStudy
Indicates that there exists a scientific study that investigates, analyzes, or provides evidence about the referenced entity or relationship.
-
C.
hasStudyModel
Indicates that an entity is associated with, or defined by, a particular study model used for analysis, simulation, or representation.
-
D.
trialDesign
Indicates the specific structure, methodology, and procedural plan according to which a trial or experiment is conducted.
-
E.
studyType
Indicates the kind or category of study or research methodology associated with an entity or activity.
- 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_69f3499da0188190ab1a4ff06fb06a2a |
completed | April 30, 2026, 12:22 p.m. |
| NER | Named-entity recognition | batch_69ff795d25d08190b7584c72be39d309 |
completed | May 9, 2026, 6:13 p.m. |
| PD | Predicate disambiguation | batch_69ff78a90fbc8190a62c57456dc1d4ad |
completed | May 9, 2026, 6:10 p.m. |
Created at: May 1, 2026, 1:50 a.m.