Triple
T25111302
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Bacteriophage T1 |
E629000
|
entity |
| Predicate | receptorOnHost |
P142668
|
FINISHED |
| Object | TonB-dependent receptor |
—
|
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: TonB-dependent receptor | Statement: [Bacteriophage T1, receptorOnHost, TonB-dependent receptor]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: receptorOnHost Context triple: [Bacteriophage T1, receptorOnHost, TonB-dependent receptor]
-
A.
receptorSystem
Indicates that one entity functions as a receptor system through which another entity receives, processes, or responds to signals or stimuli.
-
B.
receiverInterface
Indicates that one entity functions as the receiving interface or endpoint for communications, signals, or data originating from another entity.
-
C.
receptor
Indicates that one entity functions as a receptor for another, typically binding or receiving a signal, substance, or stimulus from it.
-
D.
targetsReceptor
chosen
Indicates that one entity is directed toward, binds to, or is designed to act upon a specific receptor.
-
E.
receiverAction
Indicates that the receiver of something performs or is associated with a specific action in the context of that transfer or interaction.
- 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_69e2ff3169d08190973b6061d5009abd |
completed | April 18, 2026, 3:49 a.m. |
| NER | Named-entity recognition | batch_69f46577989081909278965a9844ebad |
completed | May 1, 2026, 8:33 a.m. |
| PD | Predicate disambiguation | batch_69f44d8043b081908bbffd7f044b4f26 |
completed | May 1, 2026, 6:51 a.m. |
Created at: April 18, 2026, 6:27 a.m.