Triple
T28859111
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Preaxostyla |
E728812
|
entity |
| Predicate | hasMotility |
P187377
|
FINISHED |
| Object | flagellated |
—
|
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: flagellated | Statement: [Preaxostyla, hasMotility, flagellated]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: hasMotility Context triple: [Preaxostyla, hasMotility, flagellated]
-
A.
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).
-
B.
hasSlowMovement
Indicates that an entity exhibits movement that is slower than a normal or expected speed.
-
C.
hasAutonomousMovement
Indicates that an entity is capable of moving on its own without direct external control or intervention.
-
D.
hasOpisthodomos
Indicates that an entity (typically a building or temple) includes or is characterized by having an opisthodomos, i.e., a rear room or back chamber.
-
E.
hasMob
Indicates that an entity possesses, controls, or is associated with a particular mob or group of mobile agents.
- F. None of above. chosen
Provenance (4 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_69f031a01cbc8190ba87270bb6fe4639 |
completed | April 28, 2026, 4:03 a.m. |
| NER | Named-entity recognition | batch_69fb563aec448190875410fb1a3ed624 |
completed | May 6, 2026, 2:54 p.m. |
| PD | Predicate disambiguation | batch_69fb35b9ede881908aaae93a215525df |
completed | May 6, 2026, 12:36 p.m. |
| PDg | Predicate description generation | batch_69fb563a28d88190b28345c465c545f8 |
completed | May 6, 2026, 2:54 p.m. |
Created at: April 28, 2026, 6:46 a.m.