Triple
T30086815
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | superior frontal gyrus |
E764622
|
entity |
| Predicate | extendsAnteriorlyTo |
P87252
|
FINISHED |
| Object | frontal pole |
—
|
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: frontal pole | Statement: [superior frontal gyrus, extendsAnteriorlyTo, frontal pole]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: extendsAnteriorlyTo Context triple: [superior frontal gyrus, extendsAnteriorlyTo, frontal pole]
-
A.
anteriorPosteriorAxis
chosen
Indicates a relationship that specifies position or orientation along the front-to-back (anterior–posterior) axis of an organism or structure.
-
B.
isForwardArmOf
Indicates that one object functions as the front or leading arm/extension of another object in a given structure or system.
-
C.
isProminentPartOf
Indicates that something forms a major, highly noticeable, or significant component of a larger whole.
-
D.
isExtremityOf
Indicates that one entity is an outermost part, boundary, or terminal point of another entity.
-
E.
protrudesInto
Indicates that one entity extends outward from its own boundary so that a part of it physically enters or occupies the space of another entity.
- 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_69f67d6d35588190bf7b5ea2889ad6b8 |
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.