Triple
T28938915
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | HTT |
E730391
|
entity |
| Predicate | highExpressionIn |
P39648
|
FINISHED |
| Object | striatum |
—
|
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: striatum | Statement: [HTT, highExpressionIn, striatum]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: highExpressionIn Context triple: [HTT, highExpressionIn, striatum]
-
A.
expressedHighlyIn
chosen
Indicates that something (such as a gene, protein, or feature) is present or active at a much higher level than normal in a given entity or context.
-
B.
hasHigh
Indicates that an entity possesses a high level, degree, or intensity of a specified attribute or property.
-
C.
isHighlyRegulated
Indicates that the entity is subject to strict rules, oversight, or control by authorities or governing bodies.
-
D.
highReCharacteristic
Indicates that an entity exhibits a high Reynolds number characteristic, typically implying flow dominated by inertial rather than viscous forces.
-
E.
highestOrgan
Indicates that one entity is the organ with the highest rank, level, or position within a specified system or hierarchy relative to another entity.
- 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_69f71f8ee0688190bd025f27993452d3 |
completed | May 3, 2026, 10:12 a.m. |
| PD | Predicate disambiguation | batch_69f71cc405c08190863565609a4c8499 |
completed | May 3, 2026, 10 a.m. |
Created at: April 28, 2026, 8:34 a.m.