Triple
T22693385
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | RNA polymerase II |
E561106
|
entity |
| Predicate | hasConsensusSequence |
P149325
|
FINISHED |
| Object | YSPTSPS in CTD 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: YSPTSPS in CTD repeats | Statement: [RNA polymerase II, hasConsensusSequence, YSPTSPS in CTD repeats]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasConsensusSequence Context triple: [RNA polymerase II, hasConsensusSequence, YSPTSPS in CTD repeats]
-
A.
hasCurrentConsensus
Indicates that there is a presently agreed-upon or widely accepted position, judgment, or state regarding the related entities.
-
B.
hasTypicalSequence
Indicates that there is a usual or commonly occurring order or progression in which the related entities or events take place.
-
C.
hasConsistency
Indicates that one entity maintains a stable, uniform, or coherent state, behavior, or set of properties in relation to another entity or over time.
-
D.
hasContinuousSequence
Indicates that there exists an unbroken, ordered sequence or range connecting the related entities without gaps.
-
E.
hasSequencePosition
Indicates that an element occupies a specific position or order within a sequence.
- 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_69e2454d71b48190a1f80af9f82b6fcf |
completed | April 17, 2026, 2:35 p.m. |
| NER | Named-entity recognition | batch_69f1789c6ae481908975b7d27e7624ac |
completed | April 29, 2026, 3:18 a.m. |
| PD | Predicate disambiguation | batch_69ee62b2259c819091ed1387a748b9f3 |
completed | April 26, 2026, 7:08 p.m. |
| PDg | Predicate description generation | batch_69ee8843d3308190b6e22bb98ae5c3d8 |
completed | April 26, 2026, 9:48 p.m. |
Created at: April 17, 2026, 3:13 p.m.