Triple
T2504209
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Bacillus anthracis |
E52538
|
entity |
| Predicate | stainingCharacteristic |
P662
|
FINISHED |
| Object | forms long chains in culture |
—
|
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: forms long chains in culture | Statement: [Bacillus anthracis, stainingCharacteristic, forms long chains in culture]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: stainingCharacteristic Context triple: [Bacillus anthracis, stainingCharacteristic, forms long chains in culture]
-
A.
hasColoration
Indicates that an entity possesses a particular color or pattern of colors.
-
B.
gramStain
Indicates the result of a Gram staining procedure, specifying how an organism or sample reacts to the Gram stain (e.g., Gram-positive or Gram-negative).
-
C.
distinctiveMarking
Indicates that one entity bears a unique or distinguishing visual feature or pattern that sets it apart from others.
-
D.
stylingFeature
Indicates a visual or design-related characteristic applied to an entity, such as formatting, layout, or aesthetic treatment.
-
E.
characterizedBy
chosen
Indicates that one entity possesses a defining quality, feature, or attribute expressed by another entity.
- 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.