Triple
T25111744
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | bacteriophage lambda |
E629012
|
entity |
| Predicate | keyRegulator |
P4784
|
FINISHED |
| Object | CI repressor |
—
|
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: CI repressor | Statement: [bacteriophage lambda, keyRegulator, CI repressor]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: keyRegulator Context triple: [bacteriophage lambda, keyRegulator, CI repressor]
-
A.
primaryRegulator
chosen
Indicates that one entity serves as the main controlling or governing authority over another entity or process.
-
B.
regulatorRole
Indicates that one entity serves in an official capacity to oversee, control, or enforce rules and standards governing another entity or activity.
-
C.
regulatoryTarget
Indicates that one entity is subject to control, influence, or governance by another entity under a regulatory or rule-based framework.
-
D.
keyRule
Indicates that a rule or principle functions as a key or primary governing condition for something.
-
E.
regulatorType
Indicates the specific kind or category of regulatory role or authority associated with an 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_69f46577989081909278965a9844ebad |
completed | May 1, 2026, 8:33 a.m. |
| PD | Predicate disambiguation | batch_69f442c861188190967655c6d8012380 |
completed | May 1, 2026, 6:06 a.m. |
Created at: April 18, 2026, 6:27 a.m.