Triple
T22717255
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | one gene–one enzyme hypothesis |
E561767
|
entity |
| Predicate | refinedTo |
P44015
|
FINISHED |
| Object | one gene–one polypeptide hypothesis |
—
|
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: one gene–one polypeptide hypothesis | Statement: [one gene–one enzyme hypothesis, refinedTo, one gene–one polypeptide hypothesis]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: refinedTo Context triple: [one gene–one enzyme hypothesis, refinedTo, one gene–one polypeptide hypothesis]
-
A.
refinedIn
Indicates that one entity is processed or purified within a refining facility or operation to improve its quality or extract desired components.
-
B.
refinementBy
Indicates that one entity serves as a more detailed, precise, or improved version of another entity.
-
C.
refinedConcept
chosen
Indicates that one concept is a more precise, detailed, or specialized version of another concept.
-
D.
curatedTo
Indicates that something has been deliberately selected, organized, or refined for a particular target, purpose, or audience.
-
E.
refinesSupportFor
Indicates that one entity improves, clarifies, or makes more precise the support or justification provided by 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_69e2454fc984819088213b58ee87a002 |
completed | April 17, 2026, 2:35 p.m. |
| NER | Named-entity recognition | batch_69f1790ecbc48190926d16b20b674dbd |
completed | April 29, 2026, 3:20 a.m. |
| PD | Predicate disambiguation | batch_69ee62bd657c81909f7b01245b080a5f |
completed | April 26, 2026, 7:08 p.m. |
Created at: April 17, 2026, 3:19 p.m.