Triple
T30086813
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | superior frontal gyrus |
E764622
|
entity |
| Predicate | boundedLaterallyBy |
P168430
|
FINISHED |
| Object | superior frontal sulcus |
—
|
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: superior frontal sulcus | Statement: [superior frontal gyrus, boundedLaterallyBy, superior frontal sulcus]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: boundedLaterallyBy Context triple: [superior frontal gyrus, boundedLaterallyBy, superior frontal sulcus]
-
A.
boundedSuperiorlyBy
Indicates that one entity serves as the upper or top boundary limit of another entity.
-
B.
boundIs
Indicates that one entity is constrained, limited, or obligated by another entity, condition, or rule.
-
C.
boundedByApprox
Indicates that one quantity is constrained by another within an approximate or tolerance-based bound, rather than an exact strict limit.
-
D.
boundarySubjectTo
Indicates that a boundary is constrained, influenced, or governed by a specified subject or controlling entity.
-
E.
boundedToEastBy
Indicates that one entity’s eastern boundary is defined or limited by the presence or extent of another entity.
- 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_69f67d6d35588190bf7b5ea2889ad6b8 |
completed | May 2, 2026, 10:40 p.m. |
| PD | Predicate disambiguation | batch_69f673c664f08190b4d66cdc305e10db |
completed | May 2, 2026, 9:59 p.m. |
| PDg | Predicate description generation | batch_69f6749f205c81909d1aacf462912eee |
completed | May 2, 2026, 10:03 p.m. |
Created at: April 29, 2026, 7:04 p.m.