Triple

T30087436
Position Surface form Disambiguated ID Type / Status
Subject M2 segment E764635 entity
Predicate hasDistalBoundary P27716 FINISHED
Object M3 segment of middle 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: M3 segment of middle cerebral artery | Statement: [M2 segment, hasDistalBoundary, M3 segment of middle cerebral artery]
PD Predicate disambiguation gpt-5-mini-2025-08-07
Target predicate: hasDistalBoundary
Context triple: [M2 segment, hasDistalBoundary, M3 segment of middle cerebral artery]
  • A. hasBoundaryFeature
    Indicates that a boundary (such as an edge, border, or limit) of one entity is characterized, marked, or defined by a specific feature or element.
  • B. hasBoundarySystem
    Indicates that one entity possesses or is associated with a specific boundary system that defines its limits or separation from its surroundings.
  • C. hasBorderTerminus chosen
    Indicates that one entity serves as the endpoint or terminal location of another entity’s border or boundary.
  • D. hasBoundaryShape
    Indicates that an entity is associated with, or characterized by, a specific geometric or spatial shape of its boundary.
  • E. hasBoundaryUnit
    Indicates that one entity uses or is associated with a specific unit of measurement for its boundary or limit.
  • 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_69fd5d48855c8190bd93070b6a00d8b5 completed May 8, 2026, 3:49 a.m.
PD Predicate disambiguation batch_69fd5c9aabb88190912800d90184a89d completed May 8, 2026, 3:46 a.m.
Created at: April 29, 2026, 7:04 p.m.