Triple
T30087169
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | spinothalamic tract |
E764629
|
entity |
| Predicate | receptorInput |
P168432
|
FINISHED |
| Object | free nerve endings |
—
|
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: free nerve endings | Statement: [spinothalamic tract, receptorInput, free nerve endings]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: receptorInput Context triple: [spinothalamic tract, receptorInput, free nerve endings]
-
A.
receptor
Indicates that one entity functions as a receptor for another, typically binding or receiving a signal, substance, or stimulus from it.
-
B.
receptorSystem
Indicates that one entity functions as a receptor system through which another entity receives, processes, or responds to signals or stimuli.
-
C.
receptorTypeInteractedWith
Indicates that one entity has interacted with, bound to, or otherwise engaged a specific type of receptor.
-
D.
receiverInterface
Indicates that one entity functions as the receiving interface or endpoint for communications, signals, or data originating from another entity.
-
E.
receiverType
Indicates the category or classification of the entity that receives something (such as a message, resource, or action) in the relationship.
- 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_69f67d6d35588190bf7b5ea2889ad6b8 |
completed | May 2, 2026, 10:40 p.m. |
| PD | Predicate disambiguation | batch_69f673c664f08190b4d66cdc305e10db |
completed | May 2, 2026, 9:59 p.m. |
| PDg | Predicate description generation | batch_69f6749f205c81909d1aacf462912eee |
completed | May 2, 2026, 10:03 p.m. |
Created at: April 29, 2026, 7:04 p.m.