Triple
T28938911
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | HTT |
E730391
|
entity |
| Predicate | normalCAGRepeatRange |
P13474
|
FINISHED |
| Object | about 10–35 repeats |
—
|
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: about 10–35 repeats | Statement: [HTT, normalCAGRepeatRange, about 10–35 repeats]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: normalCAGRepeatRange Context triple: [HTT, normalCAGRepeatRange, about 10–35 repeats]
-
A.
coreRange
Indicates the primary spatial or temporal extent within which an entity, phenomenon, or relationship is predominantly present or valid.
-
B.
typicalRangeClass
Indicates that the related entity belongs to a class whose members typically fall within a characteristic or expected value range.
-
C.
typicalRange
chosen
Indicates the usual or expected range of values, conditions, or states within which something normally occurs or applies.
-
D.
normType
Indicates the specific category or classification of a norm that governs or constrains an entity or situation.
-
E.
rangeOf
Indicates that one entity specifies the set of possible values (range) that another entity’s outputs or properties can take.
- 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_69f65b81d53881908f4e8f36867d2435 |
completed | May 2, 2026, 8:16 p.m. |
| PD | Predicate disambiguation | batch_69f659d02f1c8190831758ac52bb54e4 |
completed | May 2, 2026, 8:08 p.m. |
Created at: April 28, 2026, 8:34 a.m.