Triple
T2504208
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Bacillus anthracis |
E52538
|
entity |
| Predicate | pXO2Encodes |
P14248
|
FINISHED |
| Object | capsule biosynthesis genes |
—
|
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: capsule biosynthesis genes | Statement: [Bacillus anthracis, pXO2Encodes, capsule biosynthesis genes]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: pXO2Encodes Context triple: [Bacillus anthracis, pXO2Encodes, capsule biosynthesis genes]
-
A.
encodes
chosen
Indicates that one entity contains or represents the information, instructions, or structure of another in a coded or symbolic form.
-
B.
oxygenValueApprox
Indicates that the oxygen value of an entity is approximately equal to a specified reference value, within an acceptable margin of error.
-
C.
encodedIn
Indicates that one entity is represented, stored, or expressed within another entity using a specific encoding or format.
-
D.
oxygenRequirement
Indicates the level or type of oxygen needed by an entity to live, function, or operate.
-
E.
PSE
Indicates a relationship where one entity is engaged in or associated with a public service or public sector employment role relative to another entity or context.
- 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_69ab4957b3a88190adf968ae0c1b931c |
completed | March 6, 2026, 9:38 p.m. |
| NER | Named-entity recognition | batch_69abd1cd2db0819087d21ec49ffd9585 |
completed | March 7, 2026, 7:20 a.m. |
| PD | Predicate disambiguation | batch_69abd0bba5348190bb4637d3165cb339 |
completed | March 7, 2026, 7:16 a.m. |
Created at: March 6, 2026, 9:46 p.m.