Triple
T33362262
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Green fluorescent protein |
E854252
|
entity |
| Predicate | hasAminoAcidLength |
P138253
|
FINISHED |
| Object | 238 amino acids |
—
|
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: 238 amino acids | Statement: [Green fluorescent protein, hasAminoAcidLength, 238 amino acids]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasAminoAcidLength Context triple: [Green fluorescent protein, hasAminoAcidLength, 238 amino acids]
-
A.
hasProteinLength
chosen
Indicates the length or number of amino acids in a given protein.
-
B.
hasAminoAcidAtPosition112
Indicates that a specific amino acid residue is located at position 112 in a protein or peptide sequence.
-
C.
hasAminoAcidChange
Indicates that an entity (such as a protein or gene variant) involves or results in a specific change from one amino acid to another in its sequence.
-
D.
hasNitrogenousBase
Indicates that one entity possesses or is associated with a specific nitrogenous base as a component or characteristic.
-
E.
hasProteinFeature
Indicates that a protein possesses a specific structural or functional feature, such as a domain, motif, or modification site.
- 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_69f3496bda8c8190bfc8fade9d1b791c |
completed | April 30, 2026, 12:22 p.m. |
| NER | Named-entity recognition | batch_69f6e3156ea48190b604e414665ef351 |
completed | May 3, 2026, 5:54 a.m. |
| PD | Predicate disambiguation | batch_69f6de0b9ba48190887c9eb5d06a2e94 |
completed | May 3, 2026, 5:32 a.m. |
Created at: May 1, 2026, 1:34 a.m.