Triple
T30087570
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | lenticulostriate arteries |
E764638
|
entity |
| Predicate | penetrate |
P160781
|
FINISHED |
| Object | anterior perforated substance |
—
|
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: anterior perforated substance | Statement: [lenticulostriate arteries, penetrate, anterior perforated substance]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: penetrate Context triple: [lenticulostriate arteries, penetrate, anterior perforated substance]
-
A.
يخترقها
chosen
Indicates that an entity penetrates, passes through, or breaches another entity.
-
B.
perforation
Indicates the creation or presence of a hole or series of holes made through an object or material, typically by piercing or boring.
-
C.
methodOfInfiltration
Indicates the specific technique or approach used to secretly gain access to or penetrate a target, system, or organization.
-
D.
pass
Indicates that one entity successfully transfers or moves something (such as an object, information, or a turn) to another entity.
-
E.
carvedThrough
Indicates that one entity has cut or worn a path through another entity, typically by force, motion, or gradual erosion.
- 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.