Triple
T8372336
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Huntington's chorea |
E197487
|
entity |
| Predicate | showsPhenomenon |
P58683
|
FINISHED |
| Object | anticipation |
—
|
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: anticipation | Statement: [Huntington's chorea, showsPhenomenon, anticipation]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: showsPhenomenon Context triple: [Huntington's chorea, showsPhenomenon, anticipation]
-
A.
demonstratedPhenomenon
chosen
Indicates that an entity has shown, exhibited, or provided evidence for the occurrence of a particular phenomenon.
-
B.
capturesPhenomenon
Indicates that one entity records, represents, or effectively reflects the occurrence or characteristics of a particular phenomenon.
-
C.
phenomenon
Indicates that an entity is a perceptible event, occurrence, or process that can be observed or experienced.
-
D.
showsThat
Indicates that one entity demonstrates, proves, or provides evidence for the truth or validity of another.
-
E.
hasNaturalPhenomenon
Indicates that a location, region, or environment possesses or is characterized by a particular natural phenomenon (such as a weather event, geological feature, or celestial occurrence).
- 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_69ca82f56730819080cec5d991c76f4c |
completed | March 30, 2026, 2:04 p.m. |
| NER | Named-entity recognition | batch_69cb80a6944081909c4547688c9e70ae |
completed | March 31, 2026, 8:07 a.m. |
| PD | Predicate disambiguation | batch_69cb70cd04b08190ab5f72afd22a7967 |
completed | March 31, 2026, 6:59 a.m. |
Created at: March 30, 2026, 6:01 p.m.