Triple
T37807849
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Krabbe disease |
E942551
|
entity |
| Predicate | carrierFrequency |
P189540
|
FINISHED |
| Object | increased in certain isolated populations |
—
|
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: increased in certain isolated populations | Statement: [Krabbe disease, carrierFrequency, increased in certain isolated populations]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: carrierFrequency Context triple: [Krabbe disease, carrierFrequency, increased in certain isolated populations]
-
A.
hasCarrierFrequency
Indicates that an entity (such as a signal or transmission) is associated with a specific carrier frequency at which it is transmitted or modulated.
-
B.
frequencyBand
Indicates the specific range of frequencies within which a signal, measurement, or phenomenon is defined or operates.
-
C.
frequencyBandSupported
Indicates that an entity supports operation or functionality within a specified frequency band.
-
D.
hasBroadcastFrequency
Indicates that an entity operates or transmits at a specified broadcast frequency.
-
E.
hasFrequencyChannels
Indicates that an entity is associated with, or operates over, one or more specific frequency channels.
- 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_69f76ee8104c8190ab17133ccd8f86e6 |
completed | May 3, 2026, 3:51 p.m. |
| NER | Named-entity recognition | batch_69fbc36ce1f88190a7fa1656b714e107 |
completed | May 6, 2026, 10:40 p.m. |
| PD | Predicate disambiguation | batch_69fbbd166a488190b1bf9316b0790801 |
completed | May 6, 2026, 10:13 p.m. |
| PDg | Predicate description generation | batch_69fbc36bcac48190a726b40442c094d1 |
completed | May 6, 2026, 10:40 p.m. |
Created at: May 3, 2026, 4:19 p.m.