Triple
T30087339
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | internal carotid artery |
E764633
|
entity |
| Predicate | terminatesAs |
P175261
|
FINISHED |
| Object | anterior cerebral artery |
—
|
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: anterior cerebral artery | Statement: [internal carotid artery, terminatesAs, anterior cerebral artery]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: terminatesAs Context triple: [internal carotid artery, terminatesAs, anterior cerebral artery]
-
A.
terminatesFor
Indicates that one entity causes or marks the ending or cessation of another entity, process, or state.
-
B.
terminatesOn
Indicates that one process, event, or state causes or marks the ending of another at a specific time or condition.
-
C.
terminateIn
Indicates that one entity ends, concludes, or comes to a stop within, at, or because of another entity or condition.
-
D.
typicallyTerminatedIn
Indicates that an event, process, or state usually ends or concludes in a particular way or outcome.
-
E.
terminationEndedIn
Indicates that a termination event concluded with a specific outcome or result.
- 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_69f22473c0fc8190a926a8051b3b378b |
completed | April 29, 2026, 3:32 p.m. |
| NER | Named-entity recognition | batch_69f6cee547108190ad3bc84297d8f516 |
completed | May 3, 2026, 4:28 a.m. |
| PD | Predicate disambiguation | batch_69f6cc1188708190b8f0f56e595e6057 |
completed | May 3, 2026, 4:16 a.m. |
| PDg | Predicate description generation | batch_69f6cee3604c81908a07eade2f39064e |
completed | May 3, 2026, 4:28 a.m. |
Created at: April 29, 2026, 7:04 p.m.