Triple
T1903396
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Broca's aphasia |
E37743
|
entity |
| Predicate | typicalLesionHemisphere |
P21283
|
FINISHED |
| Object | left 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: left cerebral hemisphere | Statement: [Broca's aphasia, typicalLesionHemisphere, left cerebral hemisphere]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: typicalLesionHemisphere Context triple: [Broca's aphasia, typicalLesionHemisphere, left cerebral hemisphere]
-
A.
hasPeakUsageInHemisphere
Indicates that the time period of highest usage or activity for something occurs within a specified hemisphere (e.g., Northern or Southern).
-
B.
dominantRegion
Indicates that one region exerts primary control, influence, or prominence over another region within a given context.
-
C.
operatedOnSide
Indicates that an operation or action was performed specifically on a particular side or lateral aspect of an entity.
-
D.
hasBodyRegion
chosen
Indicates that an entity possesses, includes, or is associated with a specific anatomical or bodily region.
-
E.
leftLandmark
Indicates that one entity is positioned to the left side of another entity, serving as a spatial reference point or landmark.
- 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_69a8861be7148190a680937ec451a304 |
completed | March 4, 2026, 7:21 p.m. |
| NER | Named-entity recognition | batch_69abb34d94fc8190a5bf1e582c77c725 |
completed | March 7, 2026, 5:10 a.m. |
| PD | Predicate disambiguation | batch_69abafe9f8b0819086d8f6288511c66d |
completed | March 7, 2026, 4:56 a.m. |
Created at: March 4, 2026, 7:35 p.m.