Triple
T37852083
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Anoxybacillus |
E944080
|
entity |
| Predicate | cellMotility |
P124276
|
FINISHED |
| Object | motile |
—
|
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: motile | Statement: [Anoxybacillus, cellMotility, motile]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: cellMotility Context triple: [Anoxybacillus, cellMotility, motile]
-
A.
cellBiologyFeature
chosen
Indicates a relationship where a biological entity possesses or is characterized by a specific cellular-level property, structure, or function.
-
B.
cellularOrganization
Indicates how the components within a biological cell are structured, arranged, and functionally organized in relation to one another.
-
C.
cellularComponent
Indicates the relationship between a biological entity and the specific cellular location or structure in which it is physically present or functions.
-
D.
cellDivisionMachinery
Indicates the cellular components and processes that carry out and regulate the physical division of a cell into two daughter cells.
-
E.
cellStructure
Indicates the structural organization, components, and physical arrangement that make up a cell.
- 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_69f76eed4d9c81908b1b71ba9e3b61fe |
completed | May 3, 2026, 3:51 p.m. |
| NER | Named-entity recognition | batch_69fbbae559a8819086ef839973f8d9b2 |
completed | May 6, 2026, 10:04 p.m. |
| PD | Predicate disambiguation | batch_69fbb1440fa08190abf25ba684f75b6e |
completed | May 6, 2026, 9:23 p.m. |
Created at: May 3, 2026, 4:19 p.m.