Triple
T33974906
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | RHINE |
E871107
|
entity |
| Predicate | hasStudyType |
P200184
|
FINISHED |
| Object | interventional |
—
|
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: interventional | Statement: [RHINE, hasStudyType, interventional]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasStudyType Context triple: [RHINE, hasStudyType, interventional]
-
A.
hasStudyModel
Indicates that an entity is associated with, or defined by, a particular study model used for analysis, simulation, or representation.
-
B.
hasStudied
Indicates that an entity has engaged in learning or academic work related to another entity (such as a subject, field, or course).
-
C.
hasBeenStudiedFor
Indicates that an entity has been the subject of research, examination, or analysis for a specified purpose, topic, or application.
-
D.
hasStudyAreaType
Indicates that an entity’s study area is classified as a specific type or category (e.g., lab, field site, classroom).
-
E.
isStudiedUsing
Indicates that something serves as the method, tool, or approach by which something else is examined, analyzed, or researched.
- 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_69f3499da0188190ab1a4ff06fb06a2a |
completed | April 30, 2026, 12:22 p.m. |
| NER | Named-entity recognition | batch_69ff79e7206c8190a809b5f2a6261378 |
completed | May 9, 2026, 6:16 p.m. |
| PD | Predicate disambiguation | batch_69ff798356b881908645074fb3a96517 |
completed | May 9, 2026, 6:14 p.m. |
| PDg | Predicate description generation | batch_69ff79e645c08190a974b5239efac35b |
completed | May 9, 2026, 6:16 p.m. |
Created at: May 1, 2026, 1:50 a.m.