Triple
T11467044
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | pXO2 |
E271804
|
entity |
| Predicate | absentFrom |
P14452
|
FINISHED |
| Object | many attenuated Bacillus anthracis vaccine strains |
—
|
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: many attenuated Bacillus anthracis vaccine strains | Statement: [pXO2, absentFrom, many attenuated Bacillus anthracis vaccine strains]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: absentFrom Context triple: [pXO2, absentFrom, many attenuated Bacillus anthracis vaccine strains]
-
A.
notableAbsence
chosen
Indicates that something or someone is conspicuously missing from a context where their presence would normally be expected or significant.
-
B.
attendance
Indicates the relationship between an event and the people who are present at or participate in that event.
-
C.
awayFrom
Indicates that one entity is located at a distance from, or moving farther away from, another entity.
-
D.
attendanceAnnounced
Indicates that an official statement has been made about whether and/or how many people will attend an event.
-
E.
mayAttend
Indicates that an entity is permitted or eligible to be present at or participate in a particular event, activity, or gathering.
- 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_69d6aae0c8d881908a5a360c0be3242e |
completed | April 8, 2026, 7:22 p.m. |
| NER | Named-entity recognition | batch_69d822f5eb988190b309b8e309f6d1a5 |
completed | April 9, 2026, 10:06 p.m. |
| PD | Predicate disambiguation | batch_69d80867ff248190bb157fa9e355353b |
completed | April 9, 2026, 8:13 p.m. |
Created at: April 8, 2026, 9:35 p.m.