Triple
T35664926
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Angelman syndrome |
E1030536
|
entity |
| Predicate | neurologicalFeature |
P167320
|
FINISHED |
| Object | abnormal EEG patterns |
—
|
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: abnormal EEG patterns | Statement: [Angelman syndrome, neurologicalFeature, abnormal EEG patterns]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: neurologicalFeature Context triple: [Angelman syndrome, neurologicalFeature, abnormal EEG patterns]
-
A.
hasBrainCharacteristic
chosen
Indicates that an entity possesses a specific feature, quality, or attribute related to the brain.
-
B.
lossOfFunctionPhenotype
Indicates that when a gene or gene product loses its normal function, a specific observable phenotype or trait results.
-
C.
featuresDisease
Indicates that an entity exhibits, presents, or is characterized by a particular disease.
-
D.
anatomicalFeature
Indicates that one entity is an anatomical part, structure, or feature of another entity.
-
E.
brain
Indicates that an entity functions as the brain (central cognitive or control organ) 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_69f76e09f87881909c954aaac176c34f |
completed | May 3, 2026, 3:47 p.m. |
| NER | Named-entity recognition | batch_69f79fab87b481908cd08697afe3bdd7 |
completed | May 3, 2026, 7:19 p.m. |
| PD | Predicate disambiguation | batch_69f79e4d885881908a3612e2e75cf84f |
completed | May 3, 2026, 7:13 p.m. |
Created at: May 3, 2026, 4:05 p.m.