Triple
T33287299
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Bacteriophage T2 |
E852212
|
entity |
| Predicate | hasReceptor |
P161501
|
FINISHED |
| Object | E. coli outer membrane proteins |
—
|
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: E. coli outer membrane proteins | Statement: [Bacteriophage T2, hasReceptor, E. coli outer membrane proteins]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasReceptor Context triple: [Bacteriophage T2, hasReceptor, E. coli outer membrane proteins]
-
A.
hasReceiver
Indicates that an entity serves as the recipient or target of something provided, sent, or directed by another entity.
-
B.
hasReception
Indicates that an entity hosts, includes, or is associated with a reception event (such as a formal gathering or welcoming function).
-
C.
receptor
Indicates that one entity functions as a receptor for another, typically binding or receiving a signal, substance, or stimulus from it.
-
D.
receptorTypeInteractedWith
chosen
Indicates that one entity has interacted with, bound to, or otherwise engaged a specific type of receptor.
-
E.
receptorSystem
Indicates that one entity functions as a receptor system through which another entity receives, processes, or responds to signals or stimuli.
- 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_69f349660ff48190a4568803d0b89941 |
completed | April 30, 2026, 12:21 p.m. |
| NER | Named-entity recognition | batch_6a036b0755888190a68a673664f0ea46 |
completed | May 12, 2026, 6:01 p.m. |
| PD | Predicate disambiguation | batch_6a036228676c8190aac9c90f7d8cedf7 |
completed | May 12, 2026, 5:23 p.m. |
Created at: May 1, 2026, 1:32 a.m.