Triple
T1759085
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Campylobacter |
E38614
|
entity |
| Predicate | motility |
P3596
|
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: [Campylobacter, motility, motile]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: motility Context triple: [Campylobacter, motility, motile]
-
A.
locomotion
chosen
Indicates movement or the ability to move from one place to another.
-
B.
motive
Indicates the underlying reason, intention, or driving force that explains why an entity performs or is associated with a particular action or event.
-
C.
mobilityCharacteristic
Indicates a relationship where an entity is described or classified in terms of its movement or transportation-related properties, such as how, how well, or under what conditions it can move or be moved.
-
D.
movementCharacteristic
Indicates how an entity moves or behaves in motion, such as its style, pattern, or quality of movement.
-
E.
modelsMotionOf
Indicates that one entity provides a representation or simulation of the motion or movement behavior of 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_69a8862d562481908d7025a1c1f67c0d |
completed | March 4, 2026, 7:21 p.m. |
| NER | Named-entity recognition | batch_69ab173936b4819097332ee185996bbd |
completed | March 6, 2026, 6:04 p.m. |
| PD | Predicate disambiguation | batch_69aa61c9e06c819085489e00cfe72153 |
completed | March 6, 2026, 5:10 a.m. |
Created at: March 4, 2026, 7:31 p.m.