Triple
T33287295
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Bacteriophage T2 |
E852212
|
entity |
| Predicate | hasGenomePackaging |
P193072
|
FINISHED |
| Object | headful packaging mechanism |
—
|
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: headful packaging mechanism | Statement: [Bacteriophage T2, hasGenomePackaging, headful packaging mechanism]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasGenomePackaging Context triple: [Bacteriophage T2, hasGenomePackaging, headful packaging mechanism]
-
A.
hasGenomeStructure
Indicates that one entity possesses or is characterized by a specific genome organization or arrangement.
-
B.
hasPlasmid
Indicates that one entity possesses or contains a plasmid associated with it.
-
C.
geneticMaterialOrganization
Indicates how genetic material is structured, arranged, or organized within or among biological entities.
-
D.
geneticMaterial
Indicates that one entity serves as the hereditary or genetic substance (e.g., DNA or RNA) of another entity.
-
E.
packaging
Indicates that one entity serves as the container, wrapper, or enclosing material used to package another entity.
- F. None of above. chosen
Provenance (4 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_69f349660ff48190a4568803d0b89941 |
completed | April 30, 2026, 12:21 p.m. |
| NER | Named-entity recognition | batch_69fd37b695c88190855801626f91c4cd |
completed | May 8, 2026, 1:09 a.m. |
| PD | Predicate disambiguation | batch_69fd374cccf08190a230e87164af5938 |
completed | May 8, 2026, 1:07 a.m. |
| PDg | Predicate description generation | batch_69fd37b45b4481908b947b52fbcb7ade |
completed | May 8, 2026, 1:09 a.m. |
Created at: May 1, 2026, 1:32 a.m.