Triple
T18021304
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Parasympathetic nervous system |
E431121
|
entity |
| Predicate | vagusNerveInnervates |
P129482
|
FINISHED |
| Object | heart |
—
|
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: heart | Statement: [Parasympathetic nervous system, vagusNerveInnervates, heart]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: vagusNerveInnervates Context triple: [Parasympathetic nervous system, vagusNerveInnervates, heart]
-
A.
vascularSystem
Indicates the relationship in which an entity possesses or is associated with a system of blood vessels that transports blood throughout a body.
-
B.
vascularFeature
Indicates a relationship where one entity has, exhibits, or is characterized by a particular vascular structure or property.
-
C.
regulatoryCenter
Indicates that one entity functions as an authority or hub that oversees, coordinates, or enforces rules and standards for another entity or set of activities.
-
D.
throatLocatedAt
Indicates that the throat of an entity is situated at or in contact with a specified location or body part.
-
E.
hasNervousSystem
Indicates that an entity possesses a nervous system as a biological feature.
- 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_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. |
| PDg | Predicate description generation | batch_69e42d8eefa88190a700c7c1b4213e46 |
completed | April 19, 2026, 1:19 a.m. |
Created at: April 10, 2026, 10:24 a.m.