Triple
T12019302
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Eleutherodactylidae |
E286105
|
entity |
| Predicate | typeOfLocomotion |
P3596
|
FINISHED |
| Object | saltatory locomotion |
—
|
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: saltatory locomotion | Statement: [Eleutherodactylidae, typeOfLocomotion, saltatory locomotion]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: typeOfLocomotion Context triple: [Eleutherodactylidae, typeOfLocomotion, saltatory locomotion]
-
A.
locomotion
chosen
Indicates movement or the ability to move from one place to another.
-
B.
usesStructureForLocomotion
Indicates that an entity moves or travels by employing a particular physical structure or body part as its means of locomotion.
-
C.
selfPropelled
Indicates that an entity moves or operates by its own internal power or mechanism, without needing an external force to propel it.
-
D.
hasHindLegsOf
Indicates that one entity possesses or is characterized by the hind legs belonging to or derived from another entity.
-
E.
mechanicalTransport
Indicates a relationship where an entity is moved or carried from one place to another using a mechanical means of transportation (e.g., vehicles, machines, or devices).
- 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_69d6ab45a368819084fce08bf0dc3705 |
completed | April 8, 2026, 7:23 p.m. |
| NER | Named-entity recognition | batch_69d9100b4ca8819084845ca4c13e34ce |
completed | April 10, 2026, 2:58 p.m. |
| PD | Predicate disambiguation | batch_69d902b6ebbc8190b13c44a61c6f81b9 |
completed | April 10, 2026, 2:01 p.m. |
Created at: April 8, 2026, 9:47 p.m.