Triple
T28831497
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Dermoptera |
E728061
|
entity |
| Predicate | glidingMechanism |
P165644
|
FINISHED |
| Object | passive gliding using patagium |
—
|
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: passive gliding using patagium | Statement: [Dermoptera, glidingMechanism, passive gliding using patagium]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: glidingMechanism Context triple: [Dermoptera, glidingMechanism, passive gliding using patagium]
-
A.
wingCouplingMechanism
Indicates the type or presence of a structural or functional mechanism by which wings are linked or coupled to each other or to another body part during use.
-
B.
climbingMechanism
Indicates a mechanism or method by which an entity ascends or climbs another surface or structure.
-
C.
hasSlidingMechanism
Indicates that one entity possesses or incorporates a mechanism that allows parts of it to move smoothly along a track or surface in a sliding motion.
-
D.
wingFunction
Indicates the functional role or purpose that a wing serves in enabling certain actions or capabilities.
-
E.
glideRatio
Indicates the ratio between horizontal distance traveled and vertical distance lost during a glide.
- 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_69f0319dc6088190bbfaa206d40ed74a |
completed | April 28, 2026, 4:03 a.m. |
| NER | Named-entity recognition | batch_69f6596b210481908af6cd555748f75b |
completed | May 2, 2026, 8:07 p.m. |
| PD | Predicate disambiguation | batch_69f65762b5e481908a30ca963dcba4be |
completed | May 2, 2026, 7:58 p.m. |
| PDg | Predicate description generation | batch_69f658ebeca4819096beb3f98f73fe31 |
completed | May 2, 2026, 8:05 p.m. |
Created at: April 28, 2026, 6:37 a.m.