Triple
T32025856
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Phantoms in the Brain |
E817813
|
entity |
| Predicate | settingOfResearch |
P41244
|
FINISHED |
| Object | neurology clinics |
—
|
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: neurology clinics | Statement: [Phantoms in the Brain, settingOfResearch, neurology clinics]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: settingOfResearch Context triple: [Phantoms in the Brain, settingOfResearch, neurology clinics]
-
A.
settingOfInvestigation
chosen
Indicates the context, environment, or circumstances in which an investigation takes place.
-
B.
researchMode
Indicates that an entity is engaged in or configured for conducting systematic investigation, experimentation, or study.
-
C.
studyType
Indicates the kind or category of study or research methodology associated with an entity or activity.
-
D.
researchContext
Indicates the situational, methodological, or thematic setting within which a particular piece of research is conducted or interpreted.
-
E.
purposeOfStudy
Indicates that one entity is the goal, aim, or intended objective motivating the conduct of a particular study.
- 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_69f348fb04e4819081f4eab040ed7959 |
completed | April 30, 2026, 12:20 p.m. |
| NER | Named-entity recognition | batch_69f7b2f3a104819098ddd8909eaf596c |
completed | May 3, 2026, 8:41 p.m. |
| PD | Predicate disambiguation | batch_69f7b1b8a9fc8190a1279e67a2d12707 |
completed | May 3, 2026, 8:36 p.m. |
Created at: May 1, 2026, 12:17 a.m.