Triple
T29455474
| Position | Surface form | Disambiguated ID | Type / Status |
|---|---|---|---|
| Subject | Pteromyini |
E747086
|
entity |
| Predicate | glidingMembraneExtendsFrom |
P165895
|
FINISHED |
| Object | wrist to ankle |
—
|
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: wrist to ankle | Statement: [Pteromyini, glidingMembraneExtendsFrom, wrist to ankle]
PD
Predicate disambiguation
gpt-5-mini-2025-08-07
Target predicate: glidingMembraneExtendsFrom Context triple: [Pteromyini, glidingMembraneExtendsFrom, wrist to ankle]
-
A.
glidingMechanism
Indicates a mechanism or method by which an entity moves smoothly by gliding, typically with minimal friction or powered motion.
-
B.
glidingStructure
chosen
Indicates a structure or anatomical feature that enables or is used for gliding movement through a medium such as air or water.
-
C.
hasExpansionJoints
Indicates that an object, structure, or system includes one or more expansion joints designed to accommodate movement or thermal expansion.
-
D.
mayExtendTo
Indicates that something has the potential or permission to reach, continue, or be applied up to a specified limit, scope, or boundary.
-
E.
glideRatio
Indicates the ratio between horizontal distance traveled and vertical distance lost during a glide.
- 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_69f0a7a230488190b44a97fe3d16f731 |
completed | April 28, 2026, 12:27 p.m. |
| NER | Named-entity recognition | batch_69f66b6c26a481908018e663aee7b269 |
completed | May 2, 2026, 9:23 p.m. |
| PD | Predicate disambiguation | batch_69f66339175c819080bd70f0ff7057b1 |
completed | May 2, 2026, 8:48 p.m. |
Created at: April 28, 2026, 3:36 p.m.