Triple
T37449725
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Bacteria |
E930642
|
entity |
| Predicate | canExchangeGenesBy |
P165684
|
FINISHED |
| Object | Conjugation |
—
|
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: Conjugation | Statement: [Bacteria, canExchangeGenesBy, Conjugation]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: canExchangeGenesBy Context triple: [Bacteria, canExchangeGenesBy, Conjugation]
-
A.
geneticExchange
Indicates the transfer or sharing of genetic material between entities, resulting in altered or recombined genetic information.
-
B.
hasSiblingExchange
Indicates a reciprocal relationship in which two entities are siblings of each other.
-
C.
isExchangedVia
chosen
Indicates that something is transferred or traded from one party to another through a specified medium, channel, or mechanism.
-
D.
hasInterchangesWith
Indicates that two transportation routes, lines, or services share one or more points where passengers can transfer between them.
-
E.
crossesOverWith
Indicates that one entity intersects or overlaps with another, typically by passing across or through its path, boundary, or extent.
- 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_69f76ec0b9488190b7a4fae632bd1d2f |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_69fb92efc5948190a040ba2028bab964 |
completed | May 6, 2026, 7:13 p.m. |
| PD | Predicate disambiguation | batch_69fb8d0b52588190bb29937a43b99b5e |
completed | May 6, 2026, 6:48 p.m. |
Created at: May 3, 2026, 4:17 p.m.