Triple
T30086968
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Supplementary motor area |
E764625
|
entity |
| Predicate | activationMeasuredBy |
P177570
|
FINISHED |
| Object | functional MRI |
—
|
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: functional MRI | Statement: [Supplementary motor area, activationMeasuredBy, functional MRI]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: activationMeasuredBy Context triple: [Supplementary motor area, activationMeasuredBy, functional MRI]
-
A.
enabledMeasurementOf
Indicates that one entity made it possible or allowed another entity to perform or obtain a specific measurement.
-
B.
activationConsumes
Indicates that performing an activation event uses up or depletes a specified resource.
-
C.
activatedFor
Indicates that something has been enabled, triggered, or made operational specifically on behalf of or in the context of a particular entity or target.
-
D.
activationTime
Indicates the specific point in time at which an entity, process, or function becomes active or starts operating.
-
E.
activationLevel
Indicates the degree or intensity to which something is currently active, engaged, or functioning within a given context.
- 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_69f22473c0fc8190a926a8051b3b378b |
completed | April 29, 2026, 3:32 p.m. |
| NER | Named-entity recognition | batch_69f7009d39508190af7301f824615e88 |
completed | May 3, 2026, 8 a.m. |
| PD | Predicate disambiguation | batch_69f6fc53f4f881908dcc698687bbb64d |
completed | May 3, 2026, 7:42 a.m. |
| PDg | Predicate description generation | batch_69f6ffb7554881908993d6d2ffbcf8f5 |
completed | May 3, 2026, 7:56 a.m. |
Created at: April 29, 2026, 7:04 p.m.