Triple
T10609993
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Dravet syndrome |
E275979
|
entity |
| Predicate | hasOrphanetID |
P94936
|
FINISHED |
| Object | 3308 |
—
|
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: 3308 | Statement: [Dravet syndrome, hasOrphanetID, 3308]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasOrphanetID Context triple: [Dravet syndrome, hasOrphanetID, 3308]
-
A.
hasORCID
Indicates that an entity is associated with a specific ORCID identifier, representing a unique researcher or contributor ID.
-
B.
hereditaryAssociation
Indicates a relationship in which a trait, condition, or characteristic is passed from ancestors to descendants through genetic inheritance.
-
C.
hasGeneticLocus
Indicates that a genetic feature or trait is located at, or associated with, a specific position (locus) on a genome or chromosome.
-
D.
EUAccession
Indicates that an entity becomes a member state of the European Union through the formal accession process.
-
E.
hasGeneticAffiliation
Indicates that one entity is genetically related or affiliated with another, such as sharing ancestry, lineage, or genetic characteristics.
- 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_69d6aaf948d88190806cc3a8c47a3fb2 |
completed | April 8, 2026, 7:22 p.m. |
| NER | Named-entity recognition | batch_69d6df59468881909b0c67d3f08c4b76 |
completed | April 8, 2026, 11:06 p.m. |
| PD | Predicate disambiguation | batch_69d6dd7a223c8190854409d76368f3e8 |
completed | April 8, 2026, 10:58 p.m. |
| PDg | Predicate description generation | batch_69d6df463ea8819091d6683e476b4f21 |
completed | April 8, 2026, 11:05 p.m. |
Created at: April 8, 2026, 7:32 p.m.