Triple
T28858832
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Naegleria fowleri |
E728806
|
entity |
| Predicate | motilityType |
P6160
|
FINISHED |
| Object | amoeboid movement |
—
|
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: amoeboid movement | Statement: [Naegleria fowleri, motilityType, amoeboid movement]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: motilityType Context triple: [Naegleria fowleri, motilityType, amoeboid movement]
-
A.
movementTypeDescribed
Indicates that a particular type or manner of movement is being specified or characterized.
-
B.
movementType
chosen
Indicates the manner or mode in which an entity moves or is moved from one place or state to another.
-
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.
mobilityMethod
Indicates the means or method by which an entity moves or is transported from one place to another.
-
E.
hasMobilityConcept
Indicates a relationship where an entity is associated with, or characterized by, a specific concept or model of mobility (e.g., movement, transportation, or locomotion).
- 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_69f0319f4e5481909e4c439dbe8be940 |
completed | April 28, 2026, 4:03 a.m. |
| NER | Named-entity recognition | batch_69f65a14eaa081908113d246dbaf86dd |
completed | May 2, 2026, 8:09 p.m. |
| PD | Predicate disambiguation | batch_69f65762b5e481908a30ca963dcba4be |
completed | May 2, 2026, 7:58 p.m. |
Created at: April 28, 2026, 6:46 a.m.