Triple
T28263761
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | anterior cerebral artery |
E712647
|
entity |
| Predicate | suppliesFunction |
P166210
|
FINISHED |
| Object | motor control of lower limbs |
—
|
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: motor control of lower limbs | Statement: [anterior cerebral artery, suppliesFunction, motor control of lower limbs]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: suppliesFunction Context triple: [anterior cerebral artery, suppliesFunction, motor control of lower limbs]
-
A.
suppliesTo
Indicates that one entity provides or delivers goods, services, or resources to another entity.
-
B.
supplyBy
Indicates that one entity is provided, furnished, or made available by another entity as its source or supplier.
-
C.
featuresSupplication
Indicates that one entity performs or exhibits an act of earnest pleading, begging, or humble request directed toward another entity.
-
D.
supportFunction
Indicates that one entity provides assistance, resources, or functionality that enables or enhances the operation or effectiveness of another entity.
-
E.
suppliesCity
Indicates that one entity provides goods, resources, or services to a city.
- 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_69efb5216c6881908020dce4aea65381 |
completed | April 27, 2026, 7:12 p.m. |
| NER | Named-entity recognition | batch_69f66003a3f48190a2ba6da5aafbb5cb |
completed | May 2, 2026, 8:35 p.m. |
| PD | Predicate disambiguation | batch_69f65c2198208190a3954086c22cfcbf |
completed | May 2, 2026, 8:18 p.m. |
| PDg | Predicate description generation | batch_69f65f75ac608190a62cd6afce14f68e |
completed | May 2, 2026, 8:32 p.m. |
Created at: April 27, 2026, 11:13 p.m.