Triple
T37724485
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | tuberous sclerosis complex |
E939680
|
entity |
| Predicate | canOccurAs |
P76856
|
FINISHED |
| Object | de novo mutation |
—
|
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: de novo mutation | Statement: [tuberous sclerosis complex, canOccurAs, de novo mutation]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: canOccurAs Context triple: [tuberous sclerosis complex, canOccurAs, de novo mutation]
-
A.
occursVia
Indicates that an event, process, or state happens or is realized through a specified method, mechanism, medium, or intermediary.
-
B.
occursFor
Indicates that an event, process, or condition takes place in relation to, or on behalf of, a particular entity or context.
-
C.
canBeThrownBy
Indicates that one entity is capable of being thrown or launched by another entity.
-
D.
arisesAs
chosen
Indicates that one entity comes into existence, develops, or emerges as a result, form, or manifestation of another entity or process.
-
E.
occursTo
Indicates that an event, idea, or realization happens in or comes to the mind or awareness of an 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_69f76edc208c8190bc8b9683f75e1024 |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_69fbaef0cec881908c2742d77d145901 |
completed | May 6, 2026, 9:13 p.m. |
| PD | Predicate disambiguation | batch_69fbadf632ec8190b14991c971258307 |
completed | May 6, 2026, 9:09 p.m. |
Created at: May 3, 2026, 4:18 p.m.