Triple
T25111766
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | bacteriophage lambda |
E629012
|
entity |
| Predicate | repressorMaintains |
P158186
|
FINISHED |
| Object | prophage state |
—
|
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: prophage state | Statement: [bacteriophage lambda, repressorMaintains, prophage state]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: repressorMaintains Context triple: [bacteriophage lambda, repressorMaintains, prophage state]
-
A.
maintainsThrough
Indicates that one entity preserves, upholds, or continues a state, condition, or relationship by means of another specified entity, process, or medium.
-
B.
maintainsThat
Indicates that one entity asserts, claims, or upholds a particular proposition, belief, or statement about something.
-
C.
maintainedAs
Indicates that one entity is kept in a particular state, condition, or configuration by another entity through ongoing care, management, or support.
-
D.
soughtToMaintain
Indicates an entity’s deliberate effort or intention to keep another entity or condition in its existing state over time.
-
E.
keyRegulator
chosen
Indicates that one entity plays a primary controlling or governing role over a process, system, or another entity.
- 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_69f6640168948190811bd5f933a87cf5 |
completed | May 2, 2026, 8:52 p.m. |
| PD | Predicate disambiguation | batch_69f6633451948190bcc0410602bb4914 |
completed | May 2, 2026, 8:48 p.m. |
Created at: April 18, 2026, 6:27 a.m.