Triple
T30087156
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | spinothalamic tract |
E764629
|
entity |
| Predicate | ascendsIn |
P61030
|
FINISHED |
| Object | anterolateral funiculus |
—
|
NE NERFINISHED |
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: anterolateral funiculus | Statement: [spinothalamic tract, ascendsIn, anterolateral funiculus]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: ascendsIn Context triple: [spinothalamic tract, ascendsIn, anterolateral funiculus]
-
A.
precedesInAscent
Indicates that one entity occurs or appears earlier than another in an ordered upward or ascending sequence.
-
B.
risesIn
Indicates that a river or similar watercourse originates or begins its flow in a specified location.
-
C.
endsUp
Indicates that one entity ultimately arrives at, becomes, or results in another state, condition, or location after some process or sequence of events.
-
D.
descendsOn
Indicates that one entity moves or extends downward onto or over the surface or area of another entity.
-
E.
ascendedTo
chosen
Indicates that one entity rose, climbed, or moved upward to reach the position, level, or location of another entity.
- 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_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. |
Created at: April 29, 2026, 7:04 p.m.