Triple
T33287267
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Bacteriophage T2 |
E852212
|
entity |
| Predicate | isNonEnveloped |
P54329
|
FINISHED |
| Object | true |
—
|
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: true | Statement: [Bacteriophage T2, isNonEnveloped, true]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: isNonEnveloped Context triple: [Bacteriophage T2, isNonEnveloped, true]
-
A.
enveloped
chosen
Indicates that one entity is completely or largely surrounded, covered, or enclosed by another.
-
B.
isNonBinding
Indicates that the relationship or agreement exists but does not create any legally or formally enforceable obligation between the involved entities.
-
C.
isBinaryEncoded
Indicates that information, data, or a value is represented using a binary (base-2) encoding scheme.
-
D.
hasEnvoi
Indicates that one entity includes or is associated with an envoi, typically a concluding or dedicatory section appended to a main text or composition.
-
E.
isTraditionallyWrappedWhen
Indicates that something is customarily enclosed or covered in another material or item during a particular time, event, or circumstance.
- 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_69f349660ff48190a4568803d0b89941 |
completed | April 30, 2026, 12:21 p.m. |
| NER | Named-entity recognition | batch_69f6f8164698819090c1b471f1caa4c6 |
completed | May 3, 2026, 7:24 a.m. |
| PD | Predicate disambiguation | batch_69f6f6619404819084662aef1238261c |
completed | May 3, 2026, 7:16 a.m. |
Created at: May 1, 2026, 1:32 a.m.