Triple
T30087517
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | lateral sulcus |
E764637
|
entity |
| Predicate | locatedOnSurface |
P32348
|
FINISHED |
| Object | lateral surface of cerebral hemisphere |
—
|
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: lateral surface of cerebral hemisphere | Statement: [lateral sulcus, locatedOnSurface, lateral surface of cerebral hemisphere]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: locatedOnSurface Context triple: [lateral sulcus, locatedOnSurface, lateral surface of cerebral hemisphere]
-
A.
locatedOnTerrain
Indicates that one entity is physically situated on or atop a particular terrain surface.
-
B.
locatedOnBody
chosen
Indicates that one entity is physically situated on the surface or external part of another entity’s body.
-
C.
locatedOnStructureType
Indicates that an entity is situated on or supported by a particular type of structure.
-
D.
locatedOnLevel
Indicates that one entity is situated on a specific floor or level within a multi-level structure or system.
-
E.
partlyLocatedOn
Indicates that one entity is situated such that only a portion of it lies on or within the spatial extent 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_6a00a2f0d1588190a936ea7df0ef0464 |
completed | May 10, 2026, 3:23 p.m. |
| PD | Predicate disambiguation | batch_6a00a28ccd94819085b5e123f5a4769e |
completed | May 10, 2026, 3:21 p.m. |
Created at: April 29, 2026, 7:04 p.m.