Triple
T30087579
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | lenticulostriate arteries |
E764638
|
entity |
| Predicate | commonSiteOf |
P7849
|
FINISHED |
| Object | hypertensive hemorrhage |
—
|
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: hypertensive hemorrhage | Statement: [lenticulostriate arteries, commonSiteOf, hypertensive hemorrhage]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: commonSiteOf Context triple: [lenticulostriate arteries, commonSiteOf, hypertensive hemorrhage]
-
A.
isSiteOf
chosen
Indicates that a location or place serves as the setting or host for a particular event, activity, or feature.
-
B.
commonOn
Indicates that two or more entities share the same location, context, or medium where they are present or occur together.
-
C.
primarySites
Indicates the main or originating locations associated with an entity, often distinguishing them from secondary or related sites.
-
D.
commonIn
Indicates that something frequently occurs, appears, or is found within a specified context, group, or environment.
-
E.
commonFor
Indicates that something is typical, usual, or frequently occurring for a given entity 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_69fd7fdafbe881908a31fcb407af2c34 |
completed | May 8, 2026, 6:16 a.m. |
| PD | Predicate disambiguation | batch_69fd7ef0ea908190b5d83f71565bdb1c |
completed | May 8, 2026, 6:13 a.m. |
Created at: April 29, 2026, 7:04 p.m.