Triple
T18021283
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Parasympathetic nervous system |
E431121
|
entity |
| Predicate | effectOnBladder |
P40373
|
FINISHED |
| Object | contracts detrusor muscle |
—
|
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: contracts detrusor muscle | Statement: [Parasympathetic nervous system, effectOnBladder, contracts detrusor muscle]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: effectOnBladder Context triple: [Parasympathetic nervous system, effectOnBladder, contracts detrusor muscle]
-
A.
bladderType
Indicates the specific kind or classification of bladder associated with an entity.
-
B.
isIncontinent
Indicates that an entity lacks voluntary control over urination and/or defecation.
-
C.
effectOnSystem
chosen
Indicates the influence, change, or impact that one entity, action, or condition has on the state or behavior of a system.
-
D.
effectOnUser
Indicates how an action, event, or condition influences or impacts a user.
-
E.
excretorySystem
Indicates the relationship in which an entity functions as, or is part of, the biological system responsible for removing waste products from an organism.
- 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_69d8b904530081908bf341d842464856 |
completed | April 10, 2026, 8:47 a.m. |
| NER | Named-entity recognition | batch_69e4b9c299c48190b0cceecf77cb6de9 |
completed | April 19, 2026, 11:17 a.m. |
| PD | Predicate disambiguation | batch_69e3f904b8048190add43883cd7cb191 |
completed | April 18, 2026, 9:35 p.m. |
Created at: April 10, 2026, 10:24 a.m.