Triple
T28938902
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | HTT |
E730391
|
entity |
| Predicate | hasRepeatRegion |
P10543
|
FINISHED |
| Object | polyglutamine tract |
—
|
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: polyglutamine tract | Statement: [HTT, hasRepeatRegion, polyglutamine tract]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasRepeatRegion Context triple: [HTT, hasRepeatRegion, polyglutamine tract]
-
A.
hasRepetition
Indicates that something occurs, appears, or is performed more than once, showing recurrence or repeated instances within a given context.
-
B.
hasRepetitiveHook
Indicates that something contains a recurring, catchy segment or motif that is repeated multiple times.
-
C.
hasRepetitionRate
Indicates how frequently an event, action, or pattern recurs within a given context or time frame.
-
D.
hasLoopShape
Indicates that something possesses or exhibits a form or configuration characterized by a loop-like shape.
-
E.
hasRecurringElement
chosen
Indicates that an entity includes an element that appears repeatedly or occurs multiple times within it.
- 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_69f043ea0aa88190a25acbf46157995a |
completed | April 28, 2026, 5:21 a.m. |
| NER | Named-entity recognition | batch_69ff9bed58dc8190a204816d4ed6c32c |
completed | May 9, 2026, 8:41 p.m. |
| PD | Predicate disambiguation | batch_69ff9b69653c81908ab0d88055a66a88 |
completed | May 9, 2026, 8:39 p.m. |
Created at: April 28, 2026, 8:34 a.m.