Triple
T28938839
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Huntington's disease |
E730389
|
entity |
| Predicate | showsAnticipation |
P167937
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [Huntington's disease, showsAnticipation, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: showsAnticipation Context triple: [Huntington's disease, showsAnticipation, true]
-
A.
anticipates
Indicates that one entity expects or predicts a future event, action, or state involving another entity before it actually occurs.
-
B.
showsThat
Indicates that one entity demonstrates, proves, or provides evidence for the truth or validity of another.
-
C.
ultimatelyShows
Indicates that something eventually reveals, demonstrates, or makes clear another thing as a final outcome or conclusion.
-
D.
anticipatesIdeaIn
Indicates that one entity expects, predicts, or foresees the idea or concept that will be introduced or held by another entity in a given context.
-
E.
showsFavorTo
Indicates that one entity demonstrates preference, kindness, or advantageous treatment toward another entity.
- 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_69f043ea0aa88190a25acbf46157995a |
completed | April 28, 2026, 5:21 a.m. |
| NER | Named-entity recognition | batch_69f66e5f7e30819094530abceabd5f43 |
completed | May 2, 2026, 9:36 p.m. |
| PD | Predicate disambiguation | batch_69f66abfdaf08190a55f14c70be6fd4d |
completed | May 2, 2026, 9:21 p.m. |
| PDg | Predicate description generation | batch_69f66d75a8788190aa9ca2c977429045 |
completed | May 2, 2026, 9:32 p.m. |
Created at: April 28, 2026, 8:34 a.m.