Triple
T30087634
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | angular artery |
E764639
|
entity |
| Predicate | runsSuperficialTo |
P23728
|
FINISHED |
| Object | levator labii superioris alaeque nasi muscle |
—
|
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: levator labii superioris alaeque nasi muscle | Statement: [angular artery, runsSuperficialTo, levator labii superioris alaeque nasi muscle]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: runsSuperficialTo Context triple: [angular artery, runsSuperficialTo, levator labii superioris alaeque nasi muscle]
-
A.
runsInto
Indicates that one entity moves so as to collide or come into sudden contact with another entity.
-
B.
runsBeneath
Indicates that one entity extends or moves below another entity along its length or span.
-
C.
runsDirectlyOver
chosen
Indicates that one entity passes or extends immediately above another along its length or span, without significant vertical separation or intervening structures.
-
D.
runsMostly
Indicates that an entity performs running as its primary or most frequent activity compared to other activities.
-
E.
runsAcross
Indicates that one entity moves quickly on foot from one side of another entity, area, or boundary to the opposite side, traversing it in a roughly straight path.
- 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_69f67d6de8a081909e426dcdf9fe0536 |
completed | May 2, 2026, 10:40 p.m. |
| PD | Predicate disambiguation | batch_69f673c664f08190b4d66cdc305e10db |
completed | May 2, 2026, 9:59 p.m. |
Created at: April 29, 2026, 7:04 p.m.