Triple
T29178955
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Leptospira interrogans |
E739694
|
entity |
| Predicate | motilityMechanism |
P31418
|
FINISHED |
| Object | periplasmic flagella |
—
|
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: periplasmic flagella | Statement: [Leptospira interrogans, motilityMechanism, periplasmic flagella]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: motilityMechanism Context triple: [Leptospira interrogans, motilityMechanism, periplasmic flagella]
-
A.
driveMechanism
Indicates the mechanism or component that transmits power to drive or actuate another part of a system.
-
B.
mechanismBy
Indicates that one entity occurs, is produced, or is brought about by means of another entity, which serves as its mechanism or causal process.
-
C.
locomotion
Indicates movement or the ability to move from one place to another.
-
D.
flagella
chosen
Indicates that an entity possesses or is characterized by flagella, typically referring to having one or more whip-like appendages used for movement.
-
E.
definesMechanism
Indicates that one entity specifies or explains the underlying process or mechanism by which another entity operates or occurs.
- 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_69f07cb74c2c8190ad396487fcb4fde6 |
completed | April 28, 2026, 9:24 a.m. |
| NER | Named-entity recognition | batch_69f66343216c81909f1a6503d1538608 |
completed | May 2, 2026, 8:49 p.m. |
| PD | Predicate disambiguation | batch_69f65c24f8b48190af81b575f3c15be5 |
completed | May 2, 2026, 8:18 p.m. |
Created at: April 28, 2026, 11:56 a.m.