Triple
T18088117
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Sympathetic nervous system |
E432891
|
entity |
| Predicate | originSegment |
P87048
|
FINISHED |
| Object | T1–L2 spinal cord segments |
—
|
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: T1–L2 spinal cord segments | Statement: [Sympathetic nervous system, originSegment, T1–L2 spinal cord segments]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: originSegment Context triple: [Sympathetic nervous system, originSegment, T1–L2 spinal cord segments]
-
A.
originSector
Indicates the sector or region from which an entity originally comes or was initiated.
-
B.
originatesAs
Indicates that one entity begins, arises, or comes into existence in the form, state, or role specified by another entity.
-
C.
originUse
Indicates that one entity is used as the original source, basis, or starting point for the creation, derivation, or use of another entity.
-
D.
originSite
chosen
Indicates the place or site from which something or someone originally comes or is derived.
-
E.
originalDestination
Indicates the initial or intended destination associated with an entity before any changes, rerouting, or redirection occur.
- 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_69d8b907d05c819083cc3bd6021089e6 |
completed | April 10, 2026, 8:47 a.m. |
| NER | Named-entity recognition | batch_69e4dd16234c8190b547e893a829d6c5 |
completed | April 19, 2026, 1:48 p.m. |
| PD | Predicate disambiguation | batch_69e4330e1f2881908b2506d47c48736b |
completed | April 19, 2026, 1:42 a.m. |
Created at: April 10, 2026, 10:27 a.m.