Triple
T30087532
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | lateral sulcus |
E764637
|
entity |
| Predicate | containsAtDepth |
P198258
|
FINISHED |
| Object | circular sulcus of insula |
—
|
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: circular sulcus of insula | Statement: [lateral sulcus, containsAtDepth, circular sulcus of insula]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: containsAtDepth Context triple: [lateral sulcus, containsAtDepth, circular sulcus of insula]
-
A.
occursAtDepth
Indicates that an event or phenomenon takes place at a specified depth within a medium, structure, or hierarchy.
-
B.
hasDepth
Indicates that an entity possesses a measurable extent or distance from its surface inward or from top to bottom.
-
C.
isDeeperThan
Indicates that one entity has a greater depth or is positioned further down than another entity.
-
D.
reachedDepth
Indicates that an entity has arrived at or attained a specified depth level in some medium or context.
-
E.
lowerLevelContains
Indicates that one entity includes or encompasses another entity that exists at a lower or more detailed hierarchical level.
- 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_69fed6da0390819096b88ef4714b144e |
completed | May 9, 2026, 6:40 a.m. |
| PD | Predicate disambiguation | batch_69fed53517d081909966f31707625f1a |
completed | May 9, 2026, 6:33 a.m. |
| PDg | Predicate description generation | batch_69fed6d90f2081909cd21e5e973a6b89 |
completed | May 9, 2026, 6:40 a.m. |
Created at: April 29, 2026, 7:04 p.m.