Triple
T16495028
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Aequorea victoria |
E400658
|
entity |
| Predicate | GFPApplications |
P123763
|
FINISHED |
| Object | reporter gene |
—
|
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: reporter gene | Statement: [Aequorea victoria, GFPApplications, reporter gene]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: GFPApplications Context triple: [Aequorea victoria, GFPApplications, reporter gene]
-
A.
greenFluorescentProteinSource
Indicates that one entity serves as the biological or experimental source from which green fluorescent protein (GFP) is obtained or derived for the other entity.
-
B.
greenUsedFor
Indicates that something green serves a particular purpose or function for something else.
-
C.
usesBioluminescenceFor
Indicates that an entity employs bioluminescence specifically for a particular function, purpose, or context.
-
D.
glowsInPresenceOf
Indicates that one entity emits or intensifies light when another specified entity or condition is present.
-
E.
bioluminescenceSource
Indicates that one entity is the origin or producer of the bioluminescent light exhibited by another entity.
- 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_69d88381f6148190819958a038be990e |
completed | April 10, 2026, 4:58 a.m. |
| NER | Named-entity recognition | batch_69e32e3276b88190946a669b4d893a54 |
completed | April 18, 2026, 7:09 a.m. |
| PD | Predicate disambiguation | batch_69e296902d6c8190884ddb612b8c5b36 |
completed | April 17, 2026, 8:22 p.m. |
| PDg | Predicate description generation | batch_69e2d7f97e548190a474691a152bd8e8 |
completed | April 18, 2026, 1:01 a.m. |
Created at: April 10, 2026, 5:14 a.m.