Triple
T30087102
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | reticular nucleus of thalamus |
E764628
|
entity |
| Predicate | receivesInputType |
P173743
|
FINISHED |
| Object | collaterals of thalamocortical fibers |
—
|
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: collaterals of thalamocortical fibers | Statement: [reticular nucleus of thalamus, receivesInputType, collaterals of thalamocortical fibers]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: receivesInputType Context triple: [reticular nucleus of thalamus, receivesInputType, collaterals of thalamocortical fibers]
-
A.
inputType
Indicates the kind or format of data that an entity expects to receive as input in a given context.
-
B.
hasInputType
Indicates that an entity takes another entity as its input type for its operation, function, or process.
-
C.
inputIs
Indicates that one entity serves as the input or provided value to another entity, process, or function.
-
D.
receptorInput
Indicates that a receptor receives or is provided with an input signal or stimulus from another entity.
-
E.
receivedEquipmentType
Indicates that an entity has obtained or been provided with a specific type or category of equipment.
- 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_69f6b9a84ff88190ab5a71f7ef1e0dac |
completed | May 3, 2026, 2:57 a.m. |
| PD | Predicate disambiguation | batch_69f6b626120c819097c9ad04487570d7 |
completed | May 3, 2026, 2:42 a.m. |
| PDg | Predicate description generation | batch_69f6b8fe147881908ba17483c7b13f05 |
completed | May 3, 2026, 2:54 a.m. |
Created at: April 29, 2026, 7:04 p.m.