Triple
T25111726
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | bacteriophage lambda |
E629012
|
entity |
| Predicate | integrationSite |
P158404
|
FINISHED |
| Object | between gal and bio operons in E. coli |
—
|
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: between gal and bio operons in E. coli | Statement: [bacteriophage lambda, integrationSite, between gal and bio operons in E. coli]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: integrationSite Context triple: [bacteriophage lambda, integrationSite, between gal and bio operons in E. coli]
-
A.
integrationSite
chosen
Indicates the specific location or context where one entity is incorporated or embedded into another.
-
B.
applicationSite
Indicates the location or surface where a substance, treatment, or action is applied to an entity.
-
C.
integrationFeature
Indicates that one entity provides a capability or component specifically intended to enable or support integration with another system, service, or component.
-
D.
integrationProcess
Indicates the process or workflow through which separate components, systems, or functions are combined and coordinated to operate as a unified whole.
-
E.
developmentSiteOf
Indicates that a particular site or location is the place where a specified development project or construction activity occurs or is planned to occur.
- 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_69f48b9b687881908fd87a2f5fa0b1e7 |
completed | May 1, 2026, 11:16 a.m. |
| PD | Predicate disambiguation | batch_69f48060597c8190a4414e4e4fcb1fec |
completed | May 1, 2026, 10:28 a.m. |
Created at: April 18, 2026, 6:27 a.m.