Triple
T8902319
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | middle cerebral artery |
E211957
|
entity |
| Predicate | arisesAt |
P48990
|
FINISHED |
| Object | bifurcation of internal carotid artery |
—
|
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: bifurcation of internal carotid artery | Statement: [middle cerebral artery, arisesAt, bifurcation of internal carotid artery]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: arisesAt Context triple: [middle cerebral artery, arisesAt, bifurcation of internal carotid artery]
-
A.
arisesIn
chosen
Indicates that something originates, emerges, or comes into existence within a specified context, source, or location.
-
B.
occursAt
Indicates that an event or action takes place at a specific time or location.
-
C.
raisedAt
Indicates that something was brought up, mentioned, or initiated at a particular time, place, or contextual point.
-
D.
arisesAs
Indicates that one entity comes into existence, develops, or emerges as a result, form, or manifestation of another entity or process.
-
E.
reappearsAt
Indicates that an entity, after having disappeared or been absent, becomes present again at a specific location or point in time.
- 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_69ca83918d3081909b326fa3750cb8c8 |
completed | March 30, 2026, 2:07 p.m. |
| NER | Named-entity recognition | batch_69cc642a104081908df2d64e8f9ad0c8 |
completed | April 1, 2026, 12:17 a.m. |
| PD | Predicate disambiguation | batch_69cc5ecf55248190a29f00fbf99f13c4 |
completed | March 31, 2026, 11:54 p.m. |
Created at: March 30, 2026, 6:55 p.m.