Triple
T33362259
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Green fluorescent protein |
E854252
|
entity |
| Predicate | hasChromophore |
P196512
|
FINISHED |
| Object | Ser65-Tyr66-Gly67 tripeptide |
—
|
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: Ser65-Tyr66-Gly67 tripeptide | Statement: [Green fluorescent protein, hasChromophore, Ser65-Tyr66-Gly67 tripeptide]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasChromophore Context triple: [Green fluorescent protein, hasChromophore, Ser65-Tyr66-Gly67 tripeptide]
-
A.
hasChlorophyll
Indicates that one entity possesses or contains chlorophyll, typically as a component or characteristic of its biological makeup.
-
B.
isChromatic
Indicates that something exhibits chromatic properties, such as involving or characterized by multiple colors or tones.
-
C.
hasAromaticPart
Indicates that one entity includes or contains a structural component that is aromatic.
-
D.
hasPhosphorescence
Indicates that one entity exhibits phosphorescence as a property or characteristic.
-
E.
hasChargeColor
Indicates that one entity is associated with a particular color used to represent its electric charge or charge state.
- 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_69f3496bda8c8190bfc8fade9d1b791c |
completed | April 30, 2026, 12:22 p.m. |
| NER | Named-entity recognition | batch_69fe59d11e9881909d2f33b7c717030e |
completed | May 8, 2026, 9:46 p.m. |
| PD | Predicate disambiguation | batch_69fe394fdfbc8190a931926ae3635cbf |
completed | May 8, 2026, 7:28 p.m. |
| PDg | Predicate description generation | batch_69fe59d03a648190bbe846cb5730a477 |
completed | May 8, 2026, 9:46 p.m. |
Created at: May 1, 2026, 1:34 a.m.