Triple
T37449996
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Proteus |
E930648
|
entity |
| Predicate | motilityFeature |
P187377
|
FINISHED |
| Object | swarming motility on agar |
—
|
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: swarming motility on agar | Statement: [Proteus, motilityFeature, swarming motility on agar]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: motilityFeature Context triple: [Proteus, motilityFeature, swarming motility on agar]
-
A.
hasMotility
chosen
Indicates that an entity is capable of self-directed movement or locomotion.
-
B.
motileStages
Indicates that the related entity undergoes life-cycle stages during which it is capable of movement.
-
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.
flagella
Indicates that an entity possesses or is characterized by flagella, typically referring to having one or more whip-like appendages used for movement.
-
E.
scolexFeature
Indicates that one entity is a structural or morphological feature of the scolex (the head region) 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_69f76ec0b9488190b7a4fae632bd1d2f |
completed | May 3, 2026, 3:50 p.m. |
| NER | Named-entity recognition | batch_69fb92efc5948190a040ba2028bab964 |
completed | May 6, 2026, 7:13 p.m. |
| PD | Predicate disambiguation | batch_69fb8d0b52588190bb29937a43b99b5e |
completed | May 6, 2026, 6:48 p.m. |
Created at: May 3, 2026, 4:17 p.m.