Triple
T30087563
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | lenticulostriate arteries |
E764638
|
entity |
| Predicate | supply |
P138584
|
FINISHED |
| Object | basal ganglia |
—
|
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: basal ganglia | Statement: [lenticulostriate arteries, supply, basal ganglia]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: supply Context triple: [lenticulostriate arteries, supply, basal ganglia]
-
A.
supplyBy
chosen
Indicates that one entity is provided, furnished, or made available by another entity as its source or supplier.
-
B.
supplySituation
Indicates a relationship where one entity provides or makes available needed resources, goods, or services to another under specific conditions or circumstances.
-
C.
supplyCut
Indicates that the normal provision or flow of a resource, product, or service to an entity has been reduced, interrupted, or stopped.
-
D.
supplyMode
Indicates the manner or method by which something is provided, delivered, or made available.
-
E.
supplyType
Indicates the kind or category of supply associated with or provided in a given relationship or context.
- 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_69f67d6de8a081909e426dcdf9fe0536 |
completed | May 2, 2026, 10:40 p.m. |
| PD | Predicate disambiguation | batch_69f675ff62c48190a634bbb8896973b9 |
completed | May 2, 2026, 10:09 p.m. |
Created at: April 29, 2026, 7:04 p.m.